Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openssl.pod: Move detailed text on options to new specific pages like verification.pod #13315

Closed
wants to merge 3 commits into from

Conversation

DDvO
Copy link
Contributor

@DDvO DDvO commented Nov 4, 2020

While doing #13312 I noticed again that
details on certificate verification, including a rather long list of options, are part of the top-level openssl app documentation
(and that doc/man1/openssl-verify.pod.in contains a very vague reference to openssl.pod).

I felt that this is pretty imbalanced and moved those contents to a new .pod file, adapting the various references to it.

@DDvO DDvO added the approval: otc review pending This pull request needs review by an OTC member label Nov 4, 2020
doc/man7/verification.pod Outdated Show resolved Hide resolved
@richsalz
Copy link
Contributor

richsalz commented Nov 4, 2020

The OpenSSL page has all the common options. Moving just this one set of options seems like it's a partial job; if this is necessary they should all be moved. I don't understand the "seems unbalanced" comment. This PR makes things unbalanced. :)

As a second issue, putting command line information into man7 is just plain bizarre.

Perhaps splitting openssl.pod into man1/openssl-options.pod and moving all the option sections should be done.

@DDvO
Copy link
Contributor Author

DDvO commented Nov 4, 2020

The OpenSSL page has all the common options. Moving just this one set of options seems like it's a partial job; if this is necessary they should all be moved. I don't understand the "seems unbalanced" comment. This PR makes things unbalanced. :)

It may be unbalanced in the way you state here, but I found the original state unbalanced in a different way:
heaps of detail on cert verification and its options as part of the doc of the overall openssl app.

As a second issue, putting command line information into man7 is just plain bizarre.

Your wording 'plain bizarre' is inappropriate.
I had looked it up: man7 is for mixed contents, which IMHO may be anything.

Also note that, as I wrote above to the first review comment, most of this text basically pertains to both the CLI and lib level, though the latter is not prominent and should be mentioned more explicitly.
BTW, I see this as a further imbalance, which apparently you introduced in October 2012 in commit 21d08b9.

Perhaps splitting openssl.pod into man1/openssl-options.pod and moving all the option sections should be done.

I'd prefer to move each class of options to a separate file.

@richsalz
Copy link
Contributor

richsalz commented Nov 4, 2020

BTW, I see this as a further imbalance, which apparently you introduced in October 2012 in commit 21d08b9.

Yes, the documentation at the time had too much cut and paste duplication,
and things were updated in one place and not all others, as that commit shows.

That's true.

But I think your comment is off, since that commit wasn't in October 2012 :)

Right, I confused the day with the year - the commit is of Sat Oct 12 17:45:56 2019

I seem to have offended you, and I am sorry if I did.

Fine now :)

I just found to my surprise that much of the CLI-vs-lib documentation redundancy is still there, at least regarding the verification flags, namely in doc/man3/X509_VERIFY_PARAM_set_flags.pod.

@DDvO
Copy link
Contributor Author

DDvO commented Nov 4, 2020

Oops, @richsalz by mistake I put my responses to your last comment as an edit to your comment rather than quoting it in a new comment - sorry for that.
Luckily your original response is still there (and just appears as quoted).

@DDvO DDvO force-pushed the restructure_verification_doc branch from a804273 to 5ae723a Compare November 4, 2020 16:17
@DDvO DDvO changed the title Move verification doc from doc/man1/openssl.pod to new doc/man7/verification.pod Move verification doc from openssl.pod to new openssl-verification.pod Nov 4, 2020
@DDvO
Copy link
Contributor Author

DDvO commented Nov 4, 2020

@t8m and @richsalz I meanwhile I see/agree that most of the extracted contents is still very CLI-oriented.
Therefore I've renamed doc/man7/verification.pod to doc/man1/openssl-verification.pod
and adapted the SYNOPSIS section as well as the references to the new file accordingly.

@richsalz, I agree that something similar {c,s}ould be done also for other classes of generic options,
but I do not have the time these days for further such cleanup. Feel free to help out here :)

@richsalz
Copy link
Contributor

richsalz commented Nov 4, 2020

Glad you agree, but @DDvO it's not fair to do a part-way job and hope that the rest of the work will get done by someone else :)

@DDvO
Copy link
Contributor Author

DDvO commented Nov 4, 2020

Glad you agree, but @DDvO it's not fair to do a part-way job and hope that the rest of the work will get done by someone else :)

It's pretty typical that the one who brings up an issue is the first candidate for solving it, which in this case is you ;-)

Actually there have been (and will be) loads of issues in OpenSSL (and elsewhere) where someone does an improvement while (for various reasons) does not at the same time fix further related issues.
And it's actually very natural at least in community-based projects that a change is done by someone who feels stronger than others the need for doing it.

In this case, I do not strongly feel the need for the extra changes you requested, and (as mentioned) I currently have extremely limited time, so I do what I can and need to focus on my core topic, which is certificates. If neither you nor anybody else does further improvements in the direction indicated we can open an issue such that the need for further such cleanup is not forgotten.

@richsalz
Copy link
Contributor

richsalz commented Nov 4, 2020

A couple of months ago, when some of us in the FIPS project were asking to just finish 3.0 now, to avoid slipping the schedule yet again, @mattcaswell explained that the 3.0 release is about more than just FIPS, and that OpenSSL believes it is important to have a coherent and comprehensive release.

At this point, doing something part-way goes against that thread. It is annoying to see various "part of the way there" PR's, like this one, hoping that someone else will finish off the complete task. Actually it's more than annoying.

Sure, as volunteers I understand how time is limited, and not everything is within every volunteer's level of expertise. But this particular PR isn't fixing protocol bugs, it's moving documentation around. A similar example is the "new" deprecation stuff which now has two ways of deprecating functions in header files because the original PR author wanted others to finish the job. I am sure there are other examples.

At this point, I think the project should

  • Only work on what it just voted to work on
  • Reject any PR that doesn't finish the job or leave something inconsistent.

I really think the projec

@DDvO
Copy link
Contributor Author

DDvO commented Nov 4, 2020

@richsalz, for good reason I did not indicate that this PR is targeting 3.0 - it is not really urgent.

@richsalz
Copy link
Contributor

richsalz commented Nov 4, 2020

I think "not marking it as 3.0" isn't sufficient; there are several PR's not marked that are likely to go into 3.0 (e.g., #13316, #13318, #13319, #13320, and countless others). I'd prefer to see a hold of some sort.

@DDvO DDvO force-pushed the restructure_verification_doc branch from 5ae723a to 709a310 Compare November 6, 2020 10:32
@DDvO
Copy link
Contributor Author

DDvO commented Nov 7, 2020

After resolving merge conflicts, Travis timeout out (unrelated to the doc changes done here) on one build,
so I'm kicking it by closing and re-opening this PR.

@DDvO DDvO closed this Nov 7, 2020
@DDvO DDvO reopened this Nov 7, 2020
@levitte
Copy link
Member

levitte commented Nov 8, 2020

there are several PR's not marked that are likely to go into 3.0 (e.g., #13316, #13318, #13319, #13320, and countless others)

... except all those you mention there are marked to go into 3.0.

@richsalz
Copy link
Contributor

richsalz commented Nov 8, 2020

... except all those you mention there are marked to go into 3.0.

I was wrong. I missed the milestone; I was looking only at the project field. (I still think many PR's are going to be part of 3.0 that aren't marked as such)

Since there is a post-3.0 milestone, I think this should get marked with that.

@DDvO
Copy link
Contributor Author

DDvO commented Nov 9, 2020

I am not in the position to decide on whether this PR should go into 3.0 or not.
It's not technically urgent, but I think it would be good to include rather soon due to documentation improvements included.

@DDvO
Copy link
Contributor Author

DDvO commented Nov 9, 2020

@t8m, thanks for the review you did a couple of days back.
I've addressed the comment you gave.
Do you see anything else to do/improve?

@t8m
Copy link
Member

t8m commented Nov 9, 2020

I am undecided on whether this is good change as whole or not. On one hand I agree that the openssl page is too long now and this would help making it shorter. On the other hand @richsalz has some merit in his arguments as well.

@DDvO
Copy link
Contributor Author

DDvO commented Nov 9, 2020

How about the following suggestion:

I mark this PR as WIP and hand it over to my new working student later this week,
who shall move all other overly detailed/bulky sections out of openssl.pod
basically in the same way I've done it here already for the cert verification procedure and options description?

@t8m
Copy link
Member

t8m commented Nov 9, 2020

Yep, that could be a good way forward.

@DDvO DDvO changed the title Move verification doc from openssl.pod to new openssl-verification.pod WIP: Move verification doc from openssl.pod to new openssl-verification.pod Nov 9, 2020
@DDvO DDvO force-pushed the restructure_verification_doc branch from 709a310 to 1559deb Compare November 19, 2020 15:07
@levitte
Copy link
Member

levitte commented Nov 19, 2020

While I understand the desire to split things up file wise, I can see the risk for confusion when just reading the apropos output, for the very single reason that there is no command called verification. So suddenly, we have section files with split purposes, to describe specific commands, (x)or sometimes describe some common options.

This kind of restructuring needs to mature substantially...

@DDvO
Copy link
Contributor Author

DDvO commented Nov 19, 2020

I'm also not too happy with this file name/location.
My first idea was doc/man7/verification.pod but I got pushback on that (see above).

Then I tried doc/man1/verification.pod but then ./util/find-doc-nits -n -l -e said:

doc/man1/verification.pod doesn't start with openssl-

So should I better use doc/man1/verification.pod and make ./util/find-doc-nits relax on this,
or is there any other (better) suggestion?

@DDvO DDvO force-pushed the restructure_verification_doc branch from ed06f1d to 4a4a320 Compare November 30, 2020 16:43
@DDvO DDvO changed the title WIP: openssl.pod: Move detailed text on options to new specific pages like verification.pod openssl.pod: Move detailed text on options to new specific pages like verification.pod Nov 30, 2020
@DDvO
Copy link
Contributor Author

DDvO commented Nov 30, 2020

@seardes and me have meanwhile finished moving also other bulky (likely distracting) detail on
generic options and their parameters out of openssl.pod into specific new openssl-*-options.pod files.

So I've removed the WIP: from the PR title to indicate that it is ready for review again.
Now the remaining contents of openssl.pod should be pretty balanced; let us know if you (dis)agree.

@DDvO
Copy link
Contributor Author

DDvO commented Dec 3, 2020

@seardes, could you please rebase this to fix merge conflict that meanwhile came up.

@seardes
Copy link
Contributor

seardes commented Dec 3, 2020

@seardes, could you please rebase this to fix merge conflict that meanwhile came up.

@DDvO, Will do

@DDvO DDvO force-pushed the restructure_verification_doc branch from d308fe1 to 14adc65 Compare December 4, 2020 07:11
@DDvO
Copy link
Contributor Author

DDvO commented Dec 4, 2020

@seardes, unfortunately your resolution of non-trivial merge conflicts went wrong. I've fixed this.

@DDvO
Copy link
Contributor Author

DDvO commented Dec 4, 2020

As mentioned, meanwhile we have finished extending this PR.
It's hard to keep this PR current due to high potential of non-trivlal conflicts.
@t8m, are you up for continuing your review on this?

@t8m t8m added approval: done This pull request has the required number of approvals branch: master Merge to master branch and removed approval: otc review pending This pull request needs review by an OTC member labels Dec 4, 2020
@openssl-machine openssl-machine removed the approval: done This pull request has the required number of approvals label Dec 5, 2020
@openssl-machine
Copy link
Collaborator

This pull request is ready to merge

@openssl-machine openssl-machine added the approval: ready to merge The 24 hour grace period has passed, ready to merge label Dec 5, 2020
openssl-machine pushed a commit that referenced this pull request Dec 5, 2020
…special

Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from #13315)
openssl-machine pushed a commit that referenced this pull request Dec 5, 2020
…on-options.pod

Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from #13315)
openssl-machine pushed a commit that referenced this pull request Dec 5, 2020
… and Format Options

Move detailed doc to specific new files in doc/man1/openssl-*-options.pod

Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
Reviewed-by: David von Oheimb <david.von.oheimb@siemens.com>
(Merged from #13315)
@DDvO
Copy link
Contributor Author

DDvO commented Dec 5, 2020

Merged - thanks @t8m, @richsalz, and @seardes

@DDvO DDvO closed this Dec 5, 2020

=head1 NAME

openssl-namefmt-options - DN display options
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Name display options" or "Distinguished name display options"

Also, I'm wondering if these shouldn't be exactly that throughout the manuals, "name display options". That would avoid having them mixed up with the other format options

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That includes the file name of this pod.

@@ -41,7 +41,7 @@ Print out a usage message.
=item B<-inform> B<DER>|B<PEM>

The input format; the default is B<PEM>.
See L<openssl(1)/Format Options> for details.
See L<openssl-format-options(1)/Format Options> for details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the need to include the section. L<openssl-format-options(1)> should suffice.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This applies to every such link you changed 😉

@levitte
Copy link
Member

levitte commented Dec 7, 2020

Argh, I didn't notice this was closed... sorry

@DDvO
Copy link
Contributor Author

DDvO commented Dec 7, 2020

Argh, I didn't notice this was closed... sorry

Thanks anyway @levitte for your good comments.
@seardes could you please handle those in a new PR.

@seardes
Copy link
Contributor

seardes commented Dec 7, 2020

Argh, I didn't notice this was closed... sorry

Thanks anyway @levitte for your good comments.
@seardes could you please handle those in a new PR.

@DDvO Sure, will do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approval: ready to merge The 24 hour grace period has passed, ready to merge branch: master Merge to master branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants