-
Notifications
You must be signed in to change notification settings - Fork 4
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
Task list fixes No.3 #32
base: adoc
Are you sure you want to change the base?
Conversation
One note: the manpage for grid-proxy-init looks broken at the -cert / -key option. And which actually can also be used to provide a .p12 file. In that case it seems to be looking only at the -cert option when both are present: when -cert <file.p12> is present, -key can point to any bogus file it seems. If only -key is present it is used and must be valid (e.g. a .p12). |
Concerning the old dev.globus.org page: shouldn't we import that here somewhere? I cannot check it now since the web.archive.org is down |
Did a few tests:
So one or the other alone does not work for me on Rocky Linux 9. That's most likely why both options are given like that ( Proposal
We can't, because the original site is gone and the URL forwards to the documentation site of globus. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. We still need to decide what to do with the outdated info from (now) archive.org. Perhaps just include the description of the 3 different proxy versions.
Now I understand you, you want to include that info in the documentation rather than relying on a web page that sometimes is not accessible. Hm, the relevant information there is about outdated versions of the Globus Toolkit:
According to the description the GT 4.2.x case - i.e. RFC 3820 compliant proxies are created by default and all proxy types are accepted - is still in effect. So maybe we just drop that "Compatibility" paragraph, like the corresponding manpage in the GCT source does, as GCT is compatible with all existing proxy types. |
Correction: The "Compatibility" paragraph is not only refering to compatibility but also to background information. So maybe we create a new page in our documentation that includes that background information and link to that page? |
that was indeed my thinking. Mentioning the different GT versions is probably not very useful any more unless for perhaps historic reasons. But note that it's only a few years since the legacy proxies (so basically GT2) are no longer the default (-: |
More like a decade - GT 4.2.1 is already from 2008. Or do you mean in the community? I'll come up with a page and add another commit for that. |
Ok, I have a first draft ready (attached), I also included https://web.archive.org/web/20131007221858/http://dev.globus.org/wiki/Security/ProxyFileFormat and omitted unrelated information about Java and Python code. But where should we put it? The appendices maybe, or GSI C where |
I think the appendix makes sense. It's kind of generic background information. A few comments:
|
This includes fixes for:
in the first commit and the addition of information about the use of PKCS#12 keystores with
grid-proxy-init
in the second commit.What do you think about the second commit? If you agree this information should also be added to the manpage in the GCT sources.
Could this (the documentation site and the manpage) be also a good place to reference gridcf/gct#202?