From: Junio C Hamano <gitster@pobox.com>
To: Gwyneth Morgan <gwymor@tilde.club>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] signature-format.txt: Note SSH and X.509 signature delimiters
Date: Fri, 10 Feb 2023 08:58:47 -0800 [thread overview]
Message-ID: <xmqqwn4pjw3c.fsf@gitster.g> (raw)
In-Reply-To: <Y+XhPeh76D6/Uz6C@tilde.club> (Gwyneth Morgan's message of "Fri, 10 Feb 2023 06:16:39 +0000")
Gwyneth Morgan <gwymor@tilde.club> writes:
> I believe the existing language is referring to the
> "-----BEGIN PGP MESSAGE-----" format GPG outputs in RFC 1991 mode,
> rather than the "-----BEGIN SIGNED MESSAGE-----" that X.509 uses.
The paragraph came from 76f9d8ba (Documentation/technical: describe
signature formats, 2016-06-17) that started the documentation, and
predates x509 support by two years (and ssh came even later), so
you're right. It couldn't possibly have meant anything newer.
Thanks.
> OpenSSH's signature format documentation says:
>
>
> The Armored SSH signatures consist of a header, a base64
> encoded blob, and a footer.
>
> The header is the string "-----BEGIN SSH SIGNATURE-----"
> followed by a newline. The footer is the string
> "-----END SSH SIGNATURE-----" immediately after a newline.
>
> This is sufficiently similar to the nomenclature in RFC 4880 to call
> these "Armor Header Line and Tail Line" without any misunderstanding (or
> "footer line" if that's preferred). I did not find documentation on what
> X.509 calls these.
Sounds good. Thanks for due dilligence; it would make sure our
nomenclature would not go out of line without a good reason.
next prev parent reply other threads:[~2023-02-10 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 5:32 [PATCH] signature-format.txt: Note SSH and X.509 signature delimiters Gwyneth Morgan
2022-01-20 19:30 ` Junio C Hamano
2022-01-20 19:49 ` Junio C Hamano
2023-02-10 6:16 ` Gwyneth Morgan
2023-02-10 16:58 ` Junio C Hamano [this message]
2023-02-10 6:16 ` [PATCH v2] signature-format.txt: note " Gwyneth Morgan
2023-02-10 10:52 ` Ævar Arnfjörð Bjarmason
2023-02-27 20:26 ` Gwyneth Morgan
2023-02-10 19:25 ` Junio C Hamano
2023-02-27 20:27 ` [PATCH v3] " Gwyneth Morgan
2023-02-27 21:44 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwn4pjw3c.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gwymor@tilde.club \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).