Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.os.linux > #39203 > unrolled thread

Marek Novotny GnuPG

Started byMarek Novotny <marek.novotny@marspolar.com>
First post2016-09-26 00:00 +0000
Last post2016-09-26 15:18 +0000
Articles 20 on this page of 68 — 11 participants

Back to article view | Back to alt.os.linux


Contents

  Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 00:00 +0000
    Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-25 17:32 -0700
      Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 01:04 +0000
      Re: Marek Novotny GnuPG The Letter Q <babbaquimby@teachers.org> - 2016-09-26 11:12 -0400
    Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-26 03:56 +0200
    Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 10:53 +0000
      Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 05:10 -0700
        Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 05:22 -0700
          Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 05:45 -0700
            Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 10:10 -0700
              Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 10:54 -0700
            Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 11:27 -0700
              Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-27 18:40 +0000
              Re: Marek Novotny GnuPG Bit Twister <BitTwister@mouse-potato.com> - 2016-09-27 18:41 +0000
                Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 12:06 -0700
                Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 10:14 -0700
                  Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 10:38 -0700
              Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 11:44 -0700
                Re: Marek Novotny GnuPG Melzzzzz <Melzzzzz@zzzzz.com> - 2016-09-27 19:00 +0000
                  Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 12:20 -0700
                    Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-28 00:04 +0200
                      Re: Marek Novotny GnuPG Richard Kettlewell <invalid@invalid.invalid> - 2016-09-27 23:21 +0100
                        Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 15:35 -0700
                        Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-28 00:44 +0200
                          Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 15:58 -0700
              Re: Marek Novotny GnuPG "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2016-09-27 19:24 -0400
                Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 01:06 -0700
                  Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-28 10:38 +0000
                  Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 11:21 -0700
              Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-28 10:31 +0000
                Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-28 11:24 +0000
                  Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-28 16:08 +0200
                    Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-28 19:55 +0000
                      Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 13:11 -0700
                        Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-28 22:04 +0000
                          Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-28 16:11 -0700
          Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 13:27 +0000
            Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 06:59 -0700
        Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 13:25 +0000
      Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-26 15:26 +0200
        Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 13:33 +0000
          Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-26 15:40 +0200
            Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 13:48 +0000
        Re: Marek Novotny GnuPG Richard Kettlewell <invalid@invalid.invalid> - 2016-09-26 14:39 +0100
          Re: Marek Novotny GnuPG Snit <usenet@gallopinginsanity.com> - 2016-09-26 07:00 -0700
            Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 07:26 -0700
              Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 14:53 +0000
              Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 14:59 +0000
                Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 15:01 +0000
              Re: Marek Novotny GnuPG Snit <usenet@gallopinginsanity.com> - 2016-09-26 07:34 -0700
                Re: Marek Novotny GnuPG Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-09-26 18:24 +0200
                  Re: Marek Novotny GnuPG Snit <usenet@gallopinginsanity.com> - 2016-09-26 09:30 -0700
          Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-26 16:31 +0200
            Re: Marek Novotny GnuPG Richard Kettlewell <invalid@invalid.invalid> - 2016-09-26 15:59 +0100
              Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-26 19:45 +0200
                Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 14:29 -0700
                  Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 14:37 -0700
                    Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 15:17 -0700
                      Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 23:27 +0000
          Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 15:00 -0700
            Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-26 15:34 -0700
              Re: Marek Novotny GnuPG "Carlos E.R." <robin_listas@invalid.es> - 2016-09-27 15:58 +0200
                Re: Marek Novotny GnuPG Mike Easter <MikeE@ster.invalid> - 2016-09-27 07:11 -0700
      Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 14:14 +0000
        Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 14:57 +0000
          Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 15:09 +0000
            Re: Marek Novotny GnuPG Marek Novotny <marek.novotny@marspolar.com> - 2016-09-26 15:14 +0000
            Re: Marek Novotny GnuPG Dan Purgert <dan@djph.net> - 2016-09-26 15:18 +0000

Page 1 of 4  [1] 2 3 4  Next page →


#39203 — Marek Novotny GnuPG

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-26 00:00 +0000
SubjectMarek Novotny GnuPG
Message-ID<RcadnQI3-M6t-HXKnZ2dnUU7-SPNnZ2d@giganews.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi group, 

I have added GnuPG signing to slrn and modified my signature a little to
share the public key with anyone who wishes to do verification.

The GnuPG is performed via a macro. If you're interested in added
signing and verification to slrn yourself, see this macro download page:

http://slrn.sourceforge.net/macros.html

Thanks,

- -- 
Marek Novotny
- -----------------------------------
email: marek.novotny@marspolar.com 
  Git: https://github.com/marek-novotny
GnuPG: https://www.dropbox.com/s/ey9h0bovmok5ph8/marek.novotny_pub.asc?dl=0

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJX6GUwAAoJEC9nkebvym+hK8EP/0Zbwzfstq4mS9uMzitNZ0hn
svwMQYZmHXAB8LF9TR5oZP5ObX/B8AOBEVOyP31GgcFn2rry9oU7DDimMmlJn2D3
YJ15avg6r7vmewkpEC9Bt19ysLQlnn5Ml461aNn3CyvZjeYlIXbNUD06IXcXDACF
8UGCHeUJH6Uby2je74LYo3o7aL0WsWicFISLmP0pKlhLsORPpICPWdCfoLlf2HNZ
90HkYlQ3wtBNn5ksioE337LgAQa0C8iLQdX9Axn5fifXvBhhRTrYaW1U3KbljvPE
g+pKzZ7NZ4BERy+yIbHSvZ/VgG1B6X9kBCDBOroYu3THmb3ueSiVM5osSQ8eI4Q9
TK9aGzpYs+WSgQvuBBuAjg/c9l4JuTBXZfg2iLwVzZCcXyVQKjav3G0YVNWn/3Qw
oHlX70mywt64P5ObusRgzpFOheKS0eHAqNaSSYauDaas0/CLmX2l4vYp6FILZoq2
cEL55xeLSYY3V6c9xsHBEvHDu56eAesjlxRYGsMi/HQOmrpEXEFRQ7Z+/kIFB6jz
YfRpXnAuT+BbUYou+CKizyf9fEeCBIOy5EzG86AsBsvhWK2Aa3rF7bjN39rKfhbp
uTyjETEkf0o2Uq2RlpHQC956OWSdDBbBxa5Ab5mcH6r4Ukiw3m1+9Al6Bb/VLsh9
4LwE3q33hFdXToOTIR6A
=r8Qc
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]


#39208

FromMike Easter <MikeE@ster.invalid>
Date2016-09-25 17:32 -0700
Message-ID<e4r8l8F9av6U1@mid.individual.net>
In reply to#39203
Marek Novotny wrote:
> share the public key

Your key ID 0x2F6791E6EFCA6FA1 is also at the MIT keyserver.

Some people like to just put the key fingerprint in the sig

Key fingerprint = 1646 93B2 F227 CBDB 1912  733E 2F67 91E6 EFCA 6FA1

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39209

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-26 01:04 +0000
Message-ID<1vudnXqC5c2r6XXKnZ2dnUU7-XOdnZ2d@giganews.com>
In reply to#39208
On 2016-09-26, Mike Easter <MikeE@ster.invalid> wrote:
> Marek Novotny wrote:
>> share the public key
>
> Your key ID 0x2F6791E6EFCA6FA1 is also at the MIT keyserver.

Yes, I put it in the popular keyservers around the net. 

> Some people like to just put the key fingerprint in the sig

The macro is adding the signature and actually modifying mine at the
same time. I don't think I'll need to do the signing all the time, just
once in a while when I want a simple way to say, hey, this is absolutely
me. 

> Key fingerprint = 1646 93B2 F227 CBDB 1912  733E 2F67 91E6 EFCA 6FA1

All good, thanks Mike. 

-- 
Marek Novotny
-----------------------------------
email: marek.novotny@marspolar.com 
  Git: https://github.com/marek-novotny
GnuPG: https://www.dropbox.com/s/ey9h0bovmok5ph8/marek.novotny_pub.asc?dl=0

[toc] | [prev] | [next] | [standalone]


#39244

FromThe Letter Q <babbaquimby@teachers.org>
Date2016-09-26 11:12 -0400
Message-ID<nsbdsi$dd3$1@dont-email.me>
In reply to#39208
On Sun, 25 Sep 2016 17:32:37 -0700, Mike Easter wrote:

> Marek Novotny wrote:
>> share the public key
> 
> Your key ID 0x2F6791E6EFCA6FA1 is also at the MIT keyserver.
> 
> Some people like to just put the key fingerprint in the sig
> 
> Key fingerprint = 1646 93B2 F227 CBDB 1912  733E 2F67 91E6 EFCA 6FA1

It's hilarious watching members of alt.os.linux fall to pieces just
because of snit. 
He might be wrong about some things but he is certainly right when he
says you beg for his attention.
All this PGP nonsense because of snit the troll?
Like I said, hilarious!
Keep the show going. Please!

[toc] | [prev] | [next] | [standalone]


#39210

From"Carlos E.R." <robin_listas@invalid.es>
Date2016-09-26 03:56 +0200
Message-ID<2rbmbd-cml.ln1@Telcontar.valinor>
In reply to#39203
On 2016-09-26 02:00, Marek Novotny wrote:
> Hi group,
> 
> I have added GnuPG signing to slrn and modified my signature a little to
> share the public key with anyone who wishes to do verification.

It verifies Ok.


> Yes, I put it in the popular keyservers around the net. 

Use just one. They transmit the key between them, it is a network.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]


#39216

FromDan Purgert <dan@djph.net>
Date2016-09-26 10:53 +0000
Message-ID<slrnnuhvdb.rof.dan@xps-linux.djph.net>
In reply to#39203
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marek Novotny wrote:
>
> Hi group, 
>
> I have added GnuPG signing to slrn and modified my signature a little to
> share the public key with anyone who wishes to do verification.
>
> The GnuPG is performed via a macro. If you're interested in added
> signing and verification to slrn yourself, see this macro download page:
>
> http://slrn.sourceforge.net/macros.html
>
> Thanks,
>

Nice, have thought about seeking it out off and on myself.  Seems like
now's as good a time as any to enable it.  (Here's hoping it pulls the
right key, so I don't look like a moron).

- -- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJX6P2rAAoJEI4R3fMSeaKBWGkH/RIS3UtINXhSdNmefpVMSxGd
4Too50QYAFfud7DGJwGIqfKk8NFq6c4hsjY3r8tmQCgj0OEEaS1YQJdaxWRN0oh/
tNv6mKE3Rr6PV77fDe0u+Iq8B81FgS/fKMAISxHVg3plk2UMchQRLO3z7xa2+qUc
zx5ujcqj4v7pdLlzMUnOh93X0fL29gPKhevhohGlCY56WLiwmTCZnIqPJbraF9Z+
HKfx9y6F93YIXlUB5iJshVP07qo4qmMAS8Wk6gzHJlyz8bzRY2gzY6PHglAwkNB+
4K8E//CPkN3UBkXzrR4EYuVfTfKuAmkbcFVJXefVRzXYnhRIej4xK+8HJjPRiZk=
=/UZc
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]


#39217

FromMike Easter <MikeE@ster.invalid>
Date2016-09-26 05:10 -0700
Message-ID<e4shibFichcU1@mid.individual.net>
In reply to#39216
Dan Purgert wrote:
> Marek Novotny wrote:

>> The GnuPG is performed via a macro. If you're interested in added
>> signing and verification to slrn yourself, see this macro download
>> page:

> Nice, have thought about seeking it out off and on myself.  Seems
> like now's as good a time as any to enable it.

For Tb (as opposed to slrn) users, the strategy is via gnupg and 
enigmail in the repos.

Alternatively, the enigmail .xpi Tb add-on can be downloaded from its 
webpage.  The newest there is a newer v. than in my repos.

My repo's gnupg is older (1.4.16) than required by the newest enigmail, 
so I'm better off using the older enigmail from the repos:

"This is the last major version of Enigmail to support GnuPG v1.4.x. 
Enigmail v1.9 and later will require GnuPG 2.0.7 or later."

I've also found the tool pgpdump to be useful.  Previously I used the 
online tool/version, but I found its availability to be inconsistent, so 
I got one for 'offline'/localuse.  pgpdump or gpg can be used to 
determine a sig's key id.  Naturally that isn't the way the 'web of 
trust' is supposed to work, but I find it useful/helpful.




-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39218

FromMike Easter <MikeE@ster.invalid>
Date2016-09-26 05:22 -0700
Message-ID<e4si7eFii7fU1@mid.individual.net>
In reply to#39217
Mike Easter wrote:
> My repo's gnupg is older (1.4.16) than required by the newest enigmail,
> so I'm better off using the older enigmail from the repos:

I'm running an older Mint 17.  Mint 18 & Ub 16.04 have newer gnupg 
2.1.11 (referred to as gnupg2) and enigmail 1.9.1.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39220

FromMike Easter <MikeE@ster.invalid>
Date2016-09-26 05:45 -0700
Message-ID<e4sjjlFisebU1@mid.individual.net>
In reply to#39218
Mike Easter wrote:
> Mint 18 & Ub 16.04 have newer gnupg 2.1.11 (referred to as gnupg2) and
> enigmail 1.9.1.

One reason 'this stuff' is important is not for clearsigning news 
messages.  There are MANY people who would like to secure their email, 
and encryption is the way to do it.  I frequently see reports from 
people who would like to improve that security, but find that their 
correspondents are unfamiliar with 'how to do it'.  'We' (tinw) 
shouldn't be so uninformed or 'incapable'.

The FSF has a very useful webpage and infographic on the issue.

https://emailselfdefense.fsf.org/en/  Email Self-Defense - a guide to 
fighting surveillance with GnuPG encryption

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39252

FromMike Easter <MikeE@ster.invalid>
Date2016-09-26 10:10 -0700
Message-ID<e4t33cFmmfoU1@mid.individual.net>
In reply to#39220
Mike Easter wrote:
> The FSF has a very useful webpage and infographic on the issue.
>
> https://emailselfdefense.fsf.org/en/  Email Self-Defense - a guide to
> fighting surveillance with GnuPG encryption

I've been tinkering with gnupg2 and enigmail in Tb in the live Ub 16.04 
and I like (a LOT) enigmail's 'ease of handling' and documentation.

It walks the brand new user through gentle configuration steps from 
beginner or advanced or expert who hasn't even created a keypair yet. 
That is, the handling of the key business does not require leaving enigmail.

The FSF page and philosophy include 'teach your friends' motivation to 
accommodate email security.

The combination of Tb + enigmail is a wonderful solution to Windows, 
Mac, or linux users with no skills beyond being able to setup an email 
client; so that is an excellent way to teach your friends.  Tb has an 
email wizard with algos for the majority of popular email providers.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39254

FromMike Easter <MikeE@ster.invalid>
Date2016-09-26 10:54 -0700
Message-ID<e4t5m0FnbiaU1@mid.individual.net>
In reply to#39252
Mike Easter wrote:

>> https://emailselfdefense.fsf.org/en/  Email Self-Defense - a guide to
>> fighting surveillance with GnuPG encryption
>
> It walks the brand new user through gentle configuration steps from
> beginner or advanced or expert who hasn't even created a keypair yet.
> That is, the handling of the key business does not require leaving
> enigmail.
>
FSF has also created a pgp-bot with whom you can correspond with ease, 
sending 'him'/it an email with your public key or fetching the bots key 
from the key server by using the bot's email address, or encrypting an 
email to the bot for practice, or receiving an encrypted mail from the 
bot to decrypt.


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39287

FromMike Easter <MikeE@ster.invalid>
Date2016-09-27 11:27 -0700
Message-ID<e4vs0pFcqlbU1@mid.individual.net>
In reply to#39220
Mike Easter wrote:
> Mike Easter wrote:
>> Mint 18 & Ub 16.04 have newer gnupg 2.1.11 (referred to as gnupg2)
>> and enigmail 1.9.1.
>
> One reason 'this stuff' is important is not for clearsigning news
> messages.  There are MANY people who would like to secure their email,
> and encryption is the way to do it.  I frequently see reports from
> people who would like to improve that security, but find that their
> correspondents are unfamiliar with 'how to do it'.  'We' (tinw)
> shouldn't be so uninformed or 'incapable'.

I'm still dabbling with gpg related learning/familiarization.  Presently 
I'm using both enigmail and gpa (gnu privacy assistant GUI) to handle 
the commandline gnupg for me.  And occasionally commands for something 
or other.

I was recently surprised to find that the keyserver url is apparently 
'built-in' to dirmngr.

I'm surprised at the time required by my system (the one I'm working 
with for this is not my slowest) to generate a keypair.

I would be interested in the comments of others using both strong and 
weak systems/hardware about your experiences with how long such key 
generation takes.

"Your key is being generated.  Even on fast computers this may take a 
while.  Please be patient."

The next time I do it, I'm going to set a clock (or a calendar :-)


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39288

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-27 18:40 +0000
Message-ID<J_mdnfaLlJ21IHfKnZ2dnUU7-KmdnZ2d@giganews.com>
In reply to#39287
On 2016-09-27, Mike Easter <MikeE@ster.invalid> wrote:
> Mike Easter wrote:
>> Mike Easter wrote:
>>> Mint 18 & Ub 16.04 have newer gnupg 2.1.11 (referred to as gnupg2)
>>> and enigmail 1.9.1.
>>
>> One reason 'this stuff' is important is not for clearsigning news
>> messages.  There are MANY people who would like to secure their email,
>> and encryption is the way to do it.  I frequently see reports from
>> people who would like to improve that security, but find that their
>> correspondents are unfamiliar with 'how to do it'.  'We' (tinw)
>> shouldn't be so uninformed or 'incapable'.
>
> I'm still dabbling with gpg related learning/familiarization.  Presently 
> I'm using both enigmail and gpa (gnu privacy assistant GUI) to handle 
> the commandline gnupg for me.  And occasionally commands for something 
> or other.
>
> I was recently surprised to find that the keyserver url is apparently 
> 'built-in' to dirmngr.
>
> I'm surprised at the time required by my system (the one I'm working 
> with for this is not my slowest) to generate a keypair.
>
> I would be interested in the comments of others using both strong and 
> weak systems/hardware about your experiences with how long such key 
> generation takes.
>
> "Your key is being generated.  Even on fast computers this may take a 
> while.  Please be patient."
>
> The next time I do it, I'm going to set a clock (or a calendar :-)

You can just add the {time} command as a prefix instead of watching the
clock. 

-- 
Marek Novotny
https://github.com/marek-novotny

[toc] | [prev] | [next] | [standalone]


#39289

FromBit Twister <BitTwister@mouse-potato.com>
Date2016-09-27 18:41 +0000
Message-ID<slrnnulfag.1n9.BitTwister@wb.home.test>
In reply to#39287
On Tue, 27 Sep 2016 11:27:34 -0700, Mike Easter wrote:
>
> "Your key is being generated.  Even on fast computers this may take a 
> while.  Please be patient."
>
> The next time I do it, I'm going to set a clock (or a calendar :-)

If you can use a terminal, you might consider using time.

   man time

[toc] | [prev] | [next] | [standalone]


#39292

FromMike Easter <MikeE@ster.invalid>
Date2016-09-27 12:06 -0700
Message-ID<e4vualFdc5aU1@mid.individual.net>
In reply to#39289
Bit Twister wrote:
>   man time

man time says

time --help

is supposed to print a list of commands and quit.

--help Print a summary of the command line options and exit.

-V and --version don't work either.

It isn't important for my gpg key mission anymore because the problem 
went away with the entropy, rng.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39316

FromMike Easter <MikeE@ster.invalid>
Date2016-09-28 10:14 -0700
Message-ID<e52c42Fmn5U1@mid.individual.net>
In reply to#39289
Bit Twister wrote:
> Mike Easter wrote:
>>
>> "Your key is being generated. Even on fast computers this may take
>> a while. Please be patient."
>>
>> The next time I do it, I'm going to set a clock (or a calendar :-)
>
> If you can use a terminal, you might consider using time.
>
>    man time

For my purposes, since I'm working in a GUI for gpg, I can start a 
clock/timer in the commandline and stop/end it with ^C.

time cat

then, later, at the conclusion of the keypair creation:

^C

However, I don't believe I'm really interested in timing the hang to be 
observed in the circumstances of my live boot 'no entropy' + default 
dev/random.  Instead, I'm going to start with the default live, get the 
tools, use the 'anti-hang' strategy described yesterday, and time the 
key creation under favorable circumstances instead.


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39320

FromMike Easter <MikeE@ster.invalid>
Date2016-09-28 10:38 -0700
Message-ID<e52dg1F11rrU1@mid.individual.net>
In reply to#39316
Mike Easter wrote:
> Instead, I'm going to start with the default live, get the tools, use
> the 'anti-hang' strategy described yesterday, and time the key creation
> under favorable circumstances instead.

Hmmm. My experiment didn't work because -1- the keypair was created 'too 
quickly' and -2- I (guess I) didn't know when to start the timer

I assumed that the key creation wouldn't actually begin until I had 
given the GUI prompt my passphrase, twice.

Before requesting the passphrase, the GPA GUI alerted that my 
keycreation had begun, then it prompted me for my passphrase, which 
naturally took some time/seconds to enter.  My intention was to start 
the timer as soon as I completed the passphrase entry process.

The instant my passphrase was completed the key was done.

In any case, the preparation described earlier:

install rng-tools

sudo rngd -r /dev/urandom

https://delightlylinux.wordpress.com/2015/07/01/is-gpg-hanging-when-generating-a-key/ 
  Is GPG Hanging When Generating a Key?

... makes a night&day difference in the speed of keycreation.

Just for a background on what I'm doing:

boot a live Ub Mate 16.04
install synaptic, enigmail, GPA, rng-tools
do the rngd urandom above
use GPA to make a keypair

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39290

FromMike Easter <MikeE@ster.invalid>
Date2016-09-27 11:44 -0700
Message-ID<e4vt14Fd29lU1@mid.individual.net>
In reply to#39287
Mike Easter wrote:
> I'm surprised at the time required by my system (the one I'm working
> with for this is not my slowest) to generate a keypair.

I needed more entropy, so I installed rng-tools

// rng-tools contains the rngd daemon that acts as a bridge between the 
hardware random number generator and the Linux kernel’s random number 
generator (according to Synaptic). The hang-up might be related to 
specific hardware chipsets (such as my particular motherboard), but for 
some reason, GPG works after installing rng-tools. //

The article suggests:

sudo rngd -r /dev/urandom

https://delightlylinux.wordpress.com/2015/07/01/is-gpg-hanging-when-generating-a-key/ 
  Is GPG Hanging When Generating a Key?

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


#39291

FromMelzzzzz <Melzzzzz@zzzzz.com>
Date2016-09-27 19:00 +0000
Message-ID<nsefjp$a1p$11@news.albasani.net>
In reply to#39290
On 2016-09-27, Mike Easter <MikeE@ster.invalid> wrote:
> Mike Easter wrote:
>> I'm surprised at the time required by my system (the one I'm working
>> with for this is not my slowest) to generate a keypair.
>
> I needed more entropy, so I installed rng-tools
>
> // rng-tools contains the rngd daemon that acts as a bridge between the 
> hardware random number generator and the Linux kernel’s random number 
> generator (according to Synaptic). The hang-up might be related to 
> specific hardware chipsets (such as my particular motherboard), but for 
> some reason, GPG works after installing rng-tools. //
>
> The article suggests:
>
> sudo rngd -r /dev/urandom
>
> https://delightlylinux.wordpress.com/2015/07/01/is-gpg-hanging-when-generating-a-key/ 
>   Is GPG Hanging When Generating a Key?
>
What's wrong with /dev/random ?

-- 
press any key to continue or any other to quit

[toc] | [prev] | [next] | [standalone]


#39293

FromMike Easter <MikeE@ster.invalid>
Date2016-09-27 12:20 -0700
Message-ID<e4vv3dFdig5U1@mid.individual.net>
In reply to#39291
Melzzzzz wrote:
> Mike Easter wrote:

>> The article suggests:
>>
>> sudo rngd -r /dev/urandom
>>
> What's wrong with /dev/random ?
>
If you are asking me why the article recommended urandom instead of 
random, I don't know the answer (yet) and he didn't say.

<clickety clickety>

// Fact: /dev/urandom is the preferred source of cryptographic 
randomness on UNIX-like systems. // 
http://www.2uo.de/myths-about-urandom/  Myths about /dev/urandom - by 
Thomas Hühn - There are a few things about /dev/urandom and /dev/random 
that are repeated again and again. Still they are false.


(That is an interesting/informative article, thanks for the qx.)


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]


Page 1 of 4  [1] 2 3 4  Next page →

Back to top | Article view | alt.os.linux


csiph-web