Pierre has been tasked with importing OpenSSL 3 into the base system.
Details
Details
- Reviewers
salvadore carlavilla - Group Reviewers
status - Commits
- R9:eb2d1d5c67c7: Status/2023Q2/openssl3.adoc: Add report
Diff Detail
Diff Detail
- Repository
- R9 FreeBSD doc repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
I'm not familiar with AsciiDoc yet, so I have used only plain text so far. Let me know if I should make use of its capabilities somehow.
I suppose I should also capitalize the title, or add a few links. I was not sure about the right balance for not enough or too many links; I had in mind:
- https://en.wikipedia.org/wiki/OpenSSL for the Wikipedia entry on OpenSSL
- https://en.wikipedia.org/wiki/SSLeay for the ancestor of OpenSSL
- https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/ for the OpenSSL 3.0 release notes
- https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards for FIPS
- https://www.netcraft.com/blog/june-2023-web-server-survey/ for the market share number
- https://www.linux.com/news/perl-removed-base-freebsd-sources/ (or the actual release notes for FreeBSD 5.0)
Comment Actions
Thank you very much for your report.
I think the links section is good. I would add only one link into the body of the report (see inline comment).
AsciiDoc syntax is fine, but please switch the report to use one sentence per line. Thanks.
| website/content/en/status/report-2023-04-2023-06/openssl3.adoc | ||
|---|---|---|
| 18 | Maybe check "nginx" capitalization. I would have used "Nginx", but I only find "NGINX" on the official website. I could not find anything official however. I think @grahamperrin recently fixed a nginx capitalization. @grahamperrin: what do you think about it? | |
| 35 | Well, actually 14.0 has been postponed due to OpenSSL not being part of base yet, so "in time" does not sound right to me. I would reword it. | |
| 44 | I did not know what fips is so I had to search for it: adding an explanation would be nice. The link you suggested could be enough: you can use the link macro. link:https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards[FIPS] | |
| 63 | "let it work" sounds wrong to me. Maybe "to have it working"? | |
Comment Actions
Done!
AsciiDoc syntax is fine, but please switch the report to use one sentence per line. Thanks.
Done as well.
| website/content/en/status/report-2023-04-2023-06/openssl3.adoc | ||
|---|---|---|
| 18 | About this, it's kinda weird because https://nginx.org/en/ uses "nginx" everywhere, links to the company as "Nginx, inc." at https://www.nginx.com but then https://docs.nginx.com links back to the Open Source project as "NGINX". Go figure :) | |
Comment Actions
I have pushed my branch at https://github.com/khorben/freebsd-doc/tree/khorben/report-openssl3 FWIW.
Comment Actions
Another relevant link about how to setup the FIPS module, from the documentation within OpenSSL's source code: https://github.com/openssl/openssl/blob/master/README-FIPS.md.
Comment Actions
I approve, thanks for your your report.
I think you need that I commit it for you, is that right? Shall I use Pierre Pronchery <pierre@freebsdfoundation.org> as author of the commit? By the way you should also be added to https://docs.freebsd.org/en/articles/contributors/: is that contact the one to use for that list too?
Thanks.
Comment Actions
You are correct, I do not have commit access. This name and e-mail address is also correct, and you can use this contact for the contributor list. Thank you!