Re: Proposal - variable line width for ASCII armor output
On 2/26/2020 at 11:27 AM, "Stefan Claas via Gnupg-users" wrote: >I like to make a proposal for future versions of GnuPG, >where a user can change the line witdh of ASCII armor >output. = It would not be compatible with older versions. The simplest thing for you, (or any users who prefer the aesthetics of a particular custom line width), would be to first make the GnuPG ascii armored message, then change it as you want to and copy, paste, and post, with a little note of how to change it back for verification. (fwiw, in my own experience, even the GnuPG clearsigned messages with it''s header and footer, are somewhat 'resented' in any non-crypto group, and often don't verify anyway because of minor alterations by the media posting) vedaal ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
ved...@nym.hush.com wrote: > > > On 2/26/2020 at 11:27 AM, "Stefan Claas via Gnupg-users" > wrote: > > >I like to make a proposal for future versions of GnuPG, > >where a user can change the line witdh of ASCII armor > >output. > > = > > It would not be compatible with older versions. I remember from base64 encoders which have this feature that others which don't have this that decoding still works with older decoders. And to be honest, people should keep their (privacy) software up to date, IMHO, if they like to have that feature (should it be implemented) as well ... :-) > The simplest thing for you, (or any users who prefer the aesthetics of a > particular custom line width), would be to first make the GnuPG ascii armored > message, then change it as you want to and copy, paste, and post, with a > little note of how to change it back for verification. Well, I can do that, yes, but you can't expect that all users would go the extra mile, while this could be easily implemented. Regards Stefan -- Signal (Desktop) +4915126058973 https://keybase.io/stefan_claas ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
Michał Górny wrote: > On Wed, 2020-02-26 at 13:34 -0500, vedaal via Gnupg-users wrote: > > > > On 2/26/2020 at 11:27 AM, "Stefan Claas via Gnupg-users" > > wrote: > > > > > I like to make a proposal for future versions of GnuPG, > > > where a user can change the line witdh of ASCII armor > > > output. > > > > = > > > > It would not be compatible with older versions. > > > > The simplest thing for you, (or any users who prefer the aesthetics of a > > particular custom line width), would be to first make the GnuPG ascii > > armored message, then change it as you want to and copy, paste, and post, > > with a little note of how to change it back for verification. > > > > Why 'change it back'? Unless I'm mistaken, GPG shouldn't have any real > problem with a different base64 width, as long as the overall layout is > preserved. I've just did a quick test and GPG is entirely happy with > the result after rewrapping at 50 chars, as well as after cheap > rewrapping with uneven lines. Just did a quick test ... :-) -BEGIN PGP ARMORED FILE- Comment: Use "gpg --dearmor" for unpacking VGhhbmtzIGZvciBwb2ludGluZyB0aGF0IG91dCEgSG VyZSBpcyBhIHF1aWNrCnRlc3Qgc2hvd2luZyB0aGF0 IGl0IHdvcmtzLgoKUmVnYXJkcwpTdGVmYW4K=cex4 -END PGP ARMORED FILE- Regards Stefan -- Signal (Desktop) +4915126058973 https://keybase.io/stefan_claas ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
On 2/26/2020 at 2:03 PM, "Michał Górny" wrote: > >Why 'change it back'? Unless I'm mistaken, GPG shouldn't have any >real >problem with a different base64 width, as long as the overall >layout is >preserved. I've just did a quick test and GPG is entirely happy >with >the result after rewrapping at 50 chars, as well as after cheap >rewrapping with uneven lines. Yes, but not if the header, footer, comment line, or checksum are altered. If a comment line is wrapped, and the new line does not begin with a ':' Example: This should verify: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 just a test -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Acts of Kindness better the World, and protect the Soul iQIcBAEBCAAGBQJeVsTLAAoJEFBvT6HTX7GGNRIP/1Wf7wnKYc8EF6iff3ZT6x6h TI/ipE5X5jvQNo+rhsQm2AMQXHfTY7o9gYVFqkpy2XC3mTcKi/kKeFqRr6gHjPZS DcDhsLlMEMWix/QGx8v8JAARjoaHSoXMIegOjhkjAJs07nz16EbfhIoN9AnKUcap e4/KqzpVjAjT/Q1kToV8x2gllLBtAnwp/aOG0PAYEFkgOv7RwAKpNblI5+X1skCx 1c00i5J0hyXTmIe2vp2fPJzkyuIqhAkb9IG37rH0Rm1uTq/yIeYEuw16U5OBQABy JIiBVQQDdClPuAKHKZElT/TfRsfXgDpkj5NTV3AREJGESwrQeqrGdkwU8454pivB Ukhso5KQ3iseds/qmUSMsb4G8lJ+qu1Hri1GlRGurGcjhwIeQ8TQQ2BfQ8pbVHIZ UTCOIcqIpHbgAVzRVa/UsUFiqiCkPkS3sHIF1lz5tLbnoC0E1p6e2uA2mlXtvNNt HaXPFll+Xk7U1/OuNjnFFyjUs30yDpxLT4O+46I/hioH7zGisTFjJO1iEuSO0RqO QZ3jsyjjBEhIOC9Aiko9FMhXa6MvCqIembcFQUm2v0XoZSl6PBvtBJDmVmGvLt1P GvSmaHRbRCZaiYk/KmV3d7axJQHXmt2CyFIJvw28yFh85PrGnZN6F/0TZmwZSEKh fGTZanDrJYrys3425Fd4 =/Rbe -END PGP SIGNATURE- This, with the comment line wrapped, will not: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 just a test -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Acts of Kindness better the World, and protect the Soul iQIcBAEBCAAGBQJeVsTLAAoJEFBvT6HTX7GGNRIP/1Wf7wnKYc8EF6iff3ZT6x6h TI/ipE5X5jvQNo+rhsQm2AMQXHfTY7o9gYVFqkpy2XC3mTcKi/kKeFqRr6gHjPZS DcDhsLlMEMWix/QGx8v8JAARjoaHSoXMIegOjhkjAJs07nz16EbfhIoN9AnKUcap e4/KqzpVjAjT/Q1kToV8x2gllLBtAnwp/aOG0PAYEFkgOv7RwAKpNblI5+X1skCx 1c00i5J0hyXTmIe2vp2fPJzkyuIqhAkb9IG37rH0Rm1uTq/yIeYEuw16U5OBQABy JIiBVQQDdClPuAKHKZElT/TfRsfXgDpkj5NTV3AREJGESwrQeqrGdkwU8454pivB Ukhso5KQ3iseds/qmUSMsb4G8lJ+qu1Hri1GlRGurGcjhwIeQ8TQQ2BfQ8pbVHIZ UTCOIcqIpHbgAVzRVa/UsUFiqiCkPkS3sHIF1lz5tLbnoC0E1p6e2uA2mlXtvNNt HaXPFll+Xk7U1/OuNjnFFyjUs30yDpxLT4O+46I/hioH7zGisTFjJO1iEuSO0RqO QZ3jsyjjBEhIOC9Aiko9FMhXa6MvCqIembcFQUm2v0XoZSl6PBvtBJDmVmGvLt1P GvSmaHRbRCZaiYk/KmV3d7axJQHXmt2CyFIJvw28yFh85PrGnZN6F/0TZmwZSEKh fGTZanDrJYrys3425Fd4 =/Rbe -END PGP SIGNATURE- And, this will verify, but needs the gpg.conf line of ignore-mdc-error ignore-crc-error -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 just a test -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Acts of Kindness better the World, and protect the Soul iQIcBAEBCAAGBQJeVsTLAAoJEFBvT6HTX7GGNRIP/1Wf7wnKYc8EF6iff3ZT6x6h TI/ipE5X5jvQNo+rhsQm2AMQXHfTY7o9gYVFqkpy2XC3mTcKi/kKeFqRr6gHjPZS DcDhsLlMEMWix/QGx8v8JAARjoaHSoXMIegOjhkjAJs07nz16EbfhIoN9AnKUcap e4/KqzpVjAjT/Q1kToV8x2gllLBtAnwp/aOG0PAYEFkgOv7RwAKpNblI5+X1skCx 1c00i5J0hyXTmIe2vp2fPJzkyuIqhAkb9IG37rH0Rm1uTq/yIeYEuw16U5OBQABy JIiBVQQDdClPuAKHKZElT/TfRsfXgDpkj5NTV3AREJGESwrQeqrGdkwU8454pivB Ukhso5KQ3iseds/qmUSMsb4G8lJ+qu1Hri1GlRGurGcjhwIeQ8TQQ2BfQ8pbVHIZ UTCOIcqIpHbgAVzRVa/UsUFiqiCkPkS3sHIF1lz5tLbnoC0E1p6e2uA2mlXtvNNt HaXPFll+Xk7U1/OuNjnFFyjUs30yDpxLT4O+46I/hioH7zGisTFjJO1iEuSO0RqO QZ3jsyjjBEhIOC9Aiko9FMhXa6MvCqIembcFQUm2v0XoZSl6PBvtBJDmVmGvLt1P GvSmaHRbRCZaiYk/KmV3d7axJQHXmt2CyFIJvw28yFh85PrGnZN6F/0TZmwZSEKh fGTZanDrJYrys3425Fd4=/Rbe-END PGP SIGNATURE- vedaal ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
On Wed, 2020-02-26 at 13:34 -0500, vedaal via Gnupg-users wrote: > > On 2/26/2020 at 11:27 AM, "Stefan Claas via Gnupg-users" > wrote: > > > I like to make a proposal for future versions of GnuPG, > > where a user can change the line witdh of ASCII armor > > output. > > = > > It would not be compatible with older versions. > > The simplest thing for you, (or any users who prefer the aesthetics of a > particular custom line width), > would be to first make the GnuPG ascii armored message, then change it as you > want to and copy, paste, and post, > with a little note of how to change it back for verification. > Why 'change it back'? Unless I'm mistaken, GPG shouldn't have any real problem with a different base64 width, as long as the overall layout is preserved. I've just did a quick test and GPG is entirely happy with the result after rewrapping at 50 chars, as well as after cheap rewrapping with uneven lines. -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
* Stefan Claas via Gnupg-users: > The reason why I ask, I often see postings on social > media sites and the output there looks horrible, IMHO. Fixed-width fun should do the trick. Besides, the ASCII armor format is meant to facilitate transporting key data in email, not to look pretty. Personally, I'd rather not see valuable developer time squandered on a purely aesthetic feature. -Ralph ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
Stefan Claas via Gnupg-users wrote: > Michał Górny wrote: > > > On Wed, 2020-02-26 at 13:34 -0500, vedaal via Gnupg-users wrote: > > > > > > On 2/26/2020 at 11:27 AM, "Stefan Claas via Gnupg-users" > > > wrote: > > > > > > > I like to make a proposal for future versions of GnuPG, > > > > where a user can change the line witdh of ASCII armor > > > > output. > > > > > > = > > > > > > It would not be compatible with older versions. > > > > > > The simplest thing for you, (or any users who prefer the aesthetics of a > > > particular custom line width), would be to first make the GnuPG ascii > > > armored message, then change it as you want to and copy, paste, and post, > > > with a little note of how to change it back for verification. > > > > > > > Why 'change it back'? Unless I'm mistaken, GPG shouldn't have any real > > problem with a different base64 width, as long as the overall layout is > > preserved. I've just did a quick test and GPG is entirely happy with > > the result after rewrapping at 50 chars, as well as after cheap > > rewrapping with uneven lines. > > Just did a quick test ... :-) > > -BEGIN PGP ARMORED FILE- > Comment: Use "gpg --dearmor" for unpacking > > VGhhbmtzIGZvciBwb2ludGluZyB0aGF0IG91dCEgSG > VyZSBpcyBhIHF1aWNrCnRlc3Qgc2hvd2luZyB0aGF0 > IGl0IHdvcmtzLgoKUmVnYXJkcwpTdGVmYW4K=cex4 > -END PGP ARMORED FILE- Works also nicely with signatures. :-) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Zwölf Boxkämpfer jagen Victor quer über den großen Sylter Deich. Grüße Stefan -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEUmRPI2NxNYXBCN+dVv bYx6vEHHYFAl5W+UYACgkQVvbYx6vEHHZv DQf/dFmJOOkzNQrSYYeJAEFhAKpBJp55Vu Nx94PtuZR/6oj2ZK3TRwS8tIMRfiE4W3jQ RVS2yn9WNLRvsYEPKaGxNhK9p47xR/AQHH u2m+hdd7BcvSIAt3jwbI5Zi6L9/VcCsYpV 5CsvGB/qkqtasbJjNvVf+FmLNEyqIwIR9i EBS9E57kJzZbZn2AwT9CbF9iDvvC2bo61W bP6LYrS8dDydKLQag6/kHBVksTxN/vA2Yd LLqduADCdGnVGh1SAfh94fC/rUjZjzoFHD TTIUztQK4egbITVyyg9YhBNxxCtmc/bfri P2TgESE7pl1nyB8Q3vKHCusuZRnWf1e9X8 LbHkng===bv72 Regards Stefan -- Signal (Desktop) +4915126058973 https://keybase.io/stefan_claas ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
* Stefan Claas: > I am aware of fixed-with fonts, but modern messengers or social media > do not use them. I deliberately don't use "social" media, nor do I care about it. Also, if a modern messenger (whatever you may label as such) is not supporting fixed-width fonts, that's the messenger's fault, not something to be remedied by changing GnuPG. > I guess Werner would only need a very very short time to implement > this feature among the many many many other commands and parameters > GnuPG has already accumulated over the years. :-) Any change requires design, development and testing. In the case of GnuPG across platforms. That is why I consider your specific proposal a complete waste of resources -- which is not meant as critique of you as a person. -Ralph ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
Ralph Seichter via Gnupg-users wrote: > * Stefan Claas via Gnupg-users: > > > The reason why I ask, I often see postings on social > > media sites and the output there looks horrible, IMHO. > > Fixed-width fun should do the trick. Besides, the ASCII armor format is > meant to facilitate transporting key data in email, not to look pretty. > Personally, I'd rather not see valuable developer time squandered on > a purely aesthetic feature. I am aware of fixed-with fonts, but modern messengers or social media do not use them. And about valuable developer time, I guess Werner would only need a very very short time to implement this feature among the many many many other commands and parameters GnuPG has already accumulated over the years. :-) Regards Stefan -- Signal (Desktop) +4915126058973 https://keybase.io/stefan_claas ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
Ralph Seichter via Gnupg-users wrote: > * Stefan Claas: > > > I am aware of fixed-with fonts, but modern messengers or social media > > do not use them. > > I deliberately don't use "social" media, nor do I care about it. Also, > if a modern messenger (whatever you may label as such) is not supporting > fixed-width fonts, that's the messenger's fault, not something to be > remedied by changing GnuPG. It should be noted that a fixed-width font would not help in this case, because with my proposal we are talking about a line-length paramter. Regards Stefan -- Signal (Desktop) +4915126058973 https://keybase.io/stefan_claas ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Proposal - variable line width for ASCII armor output
* Stefan Claas: > It should be noted that a fixed-width font would not help in this case, > because with my proposal we are talking about a line-length paramter. Making lines shorter to fit a vertical smartphone display? Or wider for horizontal displays? For whatever functional purpose? The key data is meant to be consumed by software, not to be visually pleasing to humans. I dare say you won't be able to convince me that your idea is beneficial in any way. ;-) -Ralph ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users