Hello All,
I even tried exporting my private and public key from the command line and then
tried
importing. The same error message as before. I have checked on the internet -
most of the
suggestions are crap - the authors have never ever tried to do what they
suggest others to
do. If they had d
Am 14.11.2014 um 12:41 schrieb da...@gbenet.com:
> Hello All,
>
> I even tried exporting my private and public key from the command line and
> then tried
> importing. The same error message as before. I have checked on the internet -
> most of the
> suggestions are crap - the authors have never
On 14/11/14 11:55, Martin Behrendt wrote:
> Am 14.11.2014 um 12:41 schrieb da...@gbenet.com:
>> Hello All,
>>
>> I even tried exporting my private and public key from the command line and
>> then tried
>> importing. The same error message as before. I have checked on the internet
>> - most of the
On 14/11/14 13:24, da...@gbenet.com wrote:
On 14/11/14 11:55, Martin Behrendt wrote:
Am 14.11.2014 um 12:41 schrieb da...@gbenet.com:
Hello All,
I even tried exporting my private and public key from the command line and then
tried
importing. The same error message as before. I have checked on
Il 14/11/2014 12:41, da...@gbenet.com ha scritto:
I usually just lurk, but that's too much...
I even tried exporting my private and public key from the command line and then
tried
importing. The same error message as before. I have checked on the internet -
most of the
suggestions are crap -
David,
It might not be clear, but many of us have easily and simply migrated our
.gnupg directories from computer to computer.
I've even deleted my .gnupg directory and restored it from backups. I've
intentionally messed up my private key and restored my private key to working
status from back
Il 14/11/2014 13:24, da...@gbenet.com ha scritto:
I have cooled. You can export your private key - you can export your public
key. You can
import your private key you can import your public key. In 20 years I have
always had the
same problem - the same error message and have each time created
On 14-11-2014 13:24, da...@gbenet.com wrote:
> I have cooled. You can export your private key - you can export your public
> key.
I've never done that, except when I imported my old pgp 2.x keys in
GnuPG a long time ago (sometime when GnuPG became really usable on
windows, with 1.0.4 or so). Exp
Am 14.11.2014 um 13:24 schrieb da...@gbenet.com:
> I have cooled.
> [...]
> Sure you can moan criticise me for my getting frustrated - and you can all
> moan and cringe
> and all withdraw your support - BUT NO ONE HAS EVER OFFERED ANY PRACTICAL
> USEFUL ADVICE THAT
> WILL ENABLE ME TO TRANSFER
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear David, dear fellow GnuPG users,
this conversation made me curious, so I tried to do it myself. Here's
what I did on my work laptop, just now, five minutes ago (in my home dir):
$ rm -rf .gnupg
$ scp -r ${myfileserver}:${pathtobackupsfromOTHERl
No one. No one. No one knows how to do this simple task.
(a) delete random_seed
(b) copy your .gnupg directory over
I don't see the problem. I've done this at least fifty different times
in the last year as I've stood up virtual machines. If you'd like a
copy of the Python script I use to do
On 14/11/14 11:47, NdK wrote:
> Il 14/11/2014 12:41, da...@gbenet.com ha scritto:
>
> I usually just lurk, but that's too much...
>
>> I even tried exporting my private and public key from the command line and
>> then tried
>> importing. The same error message as before. I have checked on the in
On 14/11/14 12:37, Samir Nassar wrote:
> David,
>
> It might not be clear, but many of us have easily and simply migrated our
> .gnupg directories from computer to computer.
>
> I've even deleted my .gnupg directory and restored it from backups. I've
> intentionally messed up my private key and
On 14/11/14 12:41, Tristan Santore wrote:
> On 14/11/14 13:24, da...@gbenet.com wrote:
>> On 14/11/14 11:55, Martin Behrendt wrote:
>>> Am 14.11.2014 um 12:41 schrieb da...@gbenet.com:
Hello All,
I even tried exporting my private and public key from the command line and
then tr
On 14/11/14 13:11, NdK wrote:
> Il 14/11/2014 13:24, da...@gbenet.com ha scritto:
>
>> I have cooled. You can export your private key - you can export your public
>> key. You can
>> import your private key you can import your public key. In 20 years I have
>> always had the
>> same problem - the
On 14/11/14 13:31, Johan Wevers wrote:
> On 14-11-2014 13:24, da...@gbenet.com wrote:
>
>> I have cooled. You can export your private key - you can export your public
>> key.
>
> I've never done that, except when I imported my old pgp 2.x keys in
> GnuPG a long time ago (sometime when GnuPG beca
On 14/11/14 13:38, Gabriel Niebler wrote:
> Dear David, dear fellow GnuPG users,
>
> this conversation made me curious, so I tried to do it myself. Here's
> what I did on my work laptop, just now, five minutes ago (in my home dir):
>
> $ rm -rf .gnupg
> $ scp -r ${myfileserver}:${pathtobackupsfro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear David,
On 14. November 2014 18:30:19 MEZ, "da...@gbenet.com" wrote:
>On 14/11/14 13:38, Gabriel Niebler wrote:
>> (...)
>> (...) maybe you can walk
>> us through exactly what you did and we'll see if we can't figure out
>> what the problem is.
Il 14/11/2014 18:24, da...@gbenet.com ha scritto:
> I have a clean install of 64 bit LXD - all programmes are working 100 per
> cent. My keys get
> imported perfectly - every programme including Enigmail knows they are there.
> But when I try
> to sign or sign and encrypt I get the error referre
On Fri, 14 Nov 2014, da...@gbenet.com wrote:
Hello All,
I even tried exporting my private and public key from the
command line and then tried importing. The same error message
as before. I have checked on the internet - most of the
suggestions are crap - the authors have never ever tried to d
On Fri, 14 Nov 2014, NdK wrote:
Il 14/11/2014 13:24, da...@gbenet.com ha scritto:
I have cooled. You can export your private key - you can export your public
key. You can
import your private key you can import your public key. In 20 years I have
always had the
same problem - the same erro
___
/| /| | |
||__|| | Please don't |
/ O O\__ feed |
/ \ the troll |
/
Something is strange, I don't know much about this stuff but it seems important
to you to have encryption working. It is so easy these days to install an OS
automagically I would, in your case, make a fresh installation on some other
machine and do what it is you want to do to prove a point. The
On Fri, 14 Nov 2014 23:28:49 +0100
Heinz Diehl wrote:
>___
> /| /| | |
> ||__|| | Please don't |
> / O O\__ feed |
>
On 15/11/14 00:11, Michael A. Yetto wrote:
On Fri, 14 Nov 2014 23:28:49 +0100
Heinz Diehl wrote:
___
/| /| | |
||__|| | Please don't |
/ O O\__
Heinz Diehl wrote:
>||__|| | Please don't |
> / O O\__ feed |
> / \ the troll |
Best forcibly un-subscribe .
Cheers,
Julian
--
Julian Stacey, BSD Linux Unix C Sys Eng Consultant Muni
On 15/11/14 03:42, Julian H. Stacey wrote:
> Heinz Diehl wrote:
>>||__|| | Please don't |
>> / O O\__ feed |
>> / \ the troll |
>
> Best forcibly un-subscribe .
>
> Cheers,
> Julian
>
Philip Jackson wrote:
> On 15/11/14 03:42, Julian H. Stacey wrote:
> > Heinz Diehl wrote:
> >>||__|| | Please don't |
> >> / O O\__ feed |
> >> / \ the troll |
> >
> > Best forcibly un-
28 matches
Mail list logo
