Re: Proposal - variable line width for ASCII armor output

2020-02-26 Thread Ralph Seichter via Gnupg-users 
* 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

Re: Proposal - variable line width for ASCII armor output

2020-02-26 Thread Stefan Claas via Gnupg-users 
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: How to create an authinfo.gpg encrypted file with a GitHub token

2020-02-26 Thread Phil Pennock via Gnupg-users 
On 2020-02-26 at 00:18 +, John Stevenson wrote:
> I would like to store a GitHub personal access token in a file called
> ~/.authinfo.gpg so that the token is not stored unencrypted on my
> computer.  This file would be used by Emacs to talk to GitHub via its API.
> 
> I have never used GnuPGP before, although I have gnupg2 installed on Ubuntu
> Linux.

Hide away GnuPG as a low-level detail and focus on "storing credentials
for use".

Take a serious look at Pass: 
which has an Emacs integration already, at:
.

(It's been 25 years since I last seriously used Emacs so I can't comment
 on that, and I don't actually use pass myself, as I independently
 created the same general thing in Python at about the same time as Pass
 was create, but the model definitely works since it works for me).

-Phil

___
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

2020-02-26 Thread Stefan Claas via Gnupg-users 
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

2020-02-26 Thread Ralph Seichter via Gnupg-users 
* 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

2020-02-26 Thread Stefan Claas via Gnupg-users 
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

2020-02-26 Thread Ralph Seichter via Gnupg-users 
* 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

GNUGP new key with old data under an old gnu version - how to fix it?

2020-02-26 Thread ADNPLANET via Gnupg-users 
Hello

I´m having this problem:

I have running a BIG system made few years ago and the programmer is not
working anymore.
The system store few data in mySQL database using gnupg encryption.
All was fine until few days ago, when the key expired. So i generate a new
one and all was perfect. But...

The new gnugp key was generated under version 2.0.22 and the data stored in
database is under gnugp 1.45
Then.. ALL new record is encrypted perfectly and appears in the database,
but the archive of a LOT records are missing, because the system is not
displaying the data encrypted with the old version.

My questions :

1 - is possible to dwongrade the GNUGP version to 1.45 in the server using
cpanel + cloudlinux and then, re-generate the key using the old 1.45
version?
2 - or is possible to update the entire database to read the encrypted data
wit the new key generated under the new version?
3 - or i´m doing something wrong ???

Thanks
Fabian

___
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

2020-02-26 Thread Michał Górny via Gnupg-users 
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

2020-02-26 Thread vedaal via Gnupg-users 
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

2020-02-26 Thread Stefan Claas via Gnupg-users 
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

2020-02-26 Thread Stefan Claas via Gnupg-users 
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

2020-02-26 Thread vedaal via Gnupg-users 



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

Proposal - variable line width for ASCII armor output

2020-02-26 Thread Stefan Claas via Gnupg-users 
Hi Werner,

I like to make a proposal for future versions of GnuPG,
where a user can change the line witdh of ASCII armor
output.

The reason why I ask, I often see postings on social
media sites and the output there looks horrible, IMHO.

For myself, I would like to have this feature when also
using such media or other chat apps etc. when I have to
reply there with GnuPG.

Mabye something like this could work gpg -a 32 etc.

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: How to create an authinfo.gpg encrypted file with a GitHub token

2020-02-26 Thread Juergen Christoffel 

On Wed, Feb 26, 2020 at 12:18:00AM +, John Stevenson wrote:

I would like to store a GitHub personal access token in a file called
~/.authinfo.gpg so that the token is not stored unencrypted on my
computer.  This file would be used by Emacs to talk to GitHub via its API.


Recent versions of Emacs (>= 23.x) offer EasyPG ("epa-mode") which handles
GnuPG encrypted files easily. That might be a good place to start looking
for what you might need. Just try to create /tmp/foo.gpg and save it. You
should be asked for a recipient and/or a key.

Or, if you're using org-mode, you could handle encrypted data there as it
offers to encrypt/decrypt certain regions of .org files:

https://orgmode.org/worg/org-tutorials/encrypting-files.html

Cheers, JC

--
 If universal surveillance were the answer, lots of us would have moved to the
 former East Germany. If surveillance cameras were the answer, camera-happy 
London,
 with something like 500,000 of them at a cost of $700 million, would be the 
safest
 city on the planet. -- Bruce Schneier

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: How to create an authinfo.gpg encrypted file with a GitHub token

2020-02-26 Thread Ralph Seichter via Gnupg-users 
* John Stevenson:

> This file would be used by Emacs to talk to GitHub via its API.

While "used by Emacs" is quite unspecific and I possibly misunderstand
your requirements, it suggests searching for "emacs gpg". Doing so
returns many hits for Easy PG, so that might be a good place to start.

-Ralph

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users