On Thu, Apr 23, 2009 at 10:28 AM, Werner Koch wrote:
>
>> Anyone know if there's a specific reason the OpenPGP standard doesn't
>> cover key ring file formats?
>
> The standard defines cares only about the format on the wire and not
> about specific implementations. You may want to use an SQL DB
> Anyone know if there's a specific reason the OpenPGP standard doesn't
> cover key ring file formats?
The standard defines cares only about the format on the wire and not
about specific implementations. You may want to use an SQL DB in one
implementation or get the key material from a punch car
On Thu, Apr 23, 2009 at 5:47 AM, Werner Koch wrote:
>
>> A platform independent set of data files means no matter what o/s you
>
> They are already platform independent. However they are bound to a
> specific gpg version. In practise there was only on minor format change
> with version 1.0.7, bu
> A platform independent set of data files means no matter what o/s you
They are already platform independent. However they are bound to a
specific gpg version. In practise there was only on minor format change
with version 1.0.7, but other changes will eventually come.
Salam-Shalom,
Werne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
that a back up export utility would be a good idea - one that selected
all the files required. Changing file formats perhaps complicates the
issue of export/import between operating systems - microsoft bringing
out "new" versions (if that made
> Yes, that's true. However, this could lead to problems if some day
> the format of GnuPG's keyring files should change, and especially
> if it should change in some architecture-specific way.
The latter won't ever happen. All file formats used by GnuPG are
platform neutral; i.e. we use well d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --
Confidentiality Statement
Wisdom is knowing what to do with what you know. This message and any
attachments are solely for the intended recipient and may contain
confidential or privileged information. If you are not the intended
recipient, any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter Pentchev escribió:
...
>> ...and set the trust level for each one again...
>
> No. That's what --export-ownertrust does.
Ah... I was not aware of that option... shame on me.
I also thought he would have to export the keys one by one... a
On Wed, Apr 22, 2009 at 11:38:55AM -0400, Faramir wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> > What's wrong with just --export ing the public/private keys, and
> > importing them into win2000?
>
> Well, if he does it that way, he would have to re-download the keys of
> h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> What's wrong with just --export ing the public/private keys, and
> importing them into win2000?
Well, if he does it that way, he would have to re-download the keys of
his contacts again, and set the trust level for each one again. If he
keeps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 22 Apr 2009 14:57:00 david wrote:
> Hi All,
>
> installing gnupg enigma on pro 2000 I have to import files from this
> linux laptop - are file conventions the same?
>
> (a) put linux hard drive on usb and scan for keys public and private
via
>
david wrote:
> Hi All,
>
> installing GnuPG Enigmail on pro 2000 I have to import files from this
> linux laptop - are file conventions the same?
At present. This may change in some future version of GnuPG
> (a) put linux hard drive on usb and scan for keys public and private via
> enigmail or g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
installing gnupg enigma on pro 2000 I have to import files from this
linux laptop - are file conventions the same?
(a) put linux hard drive on usb and scan for keys public and private via
enigmail or gui for gnupg
b) copy just the folder of
13 matches
Mail list logo
