Re: Questions about trust signatures

2008-06-13 Thread David Shaw
On Wed, Jun 11, 2008 at 04:10:28PM -0700, bezna wrote: > > Dear GnuPG users, > > I have some questions regarding use of the tsign command; please don't feel > you have to answer all of them at once, just one will do, although I'd like > to point out that the one most important to me is #1. I???ve

Re: Remove public key from secret key

2008-06-13 Thread David Shaw
On Mon, Jun 09, 2008 at 11:46:28PM -0400, Ivan Peev wrote: > Hello Guys, > > Is there a way to export the secret key without the public key or remove the > public key from exported secret key? I'm trying the following scenario: > > 1. Encrypt data with particular public key on one machine. > 2. D

Re: passphrases: the police and subkeys scenario

2008-06-13 Thread David Shaw
On Wed, Jun 11, 2008 at 03:41:05PM -0400, Rick Valenzuela wrote: > I'm now confused about creating a separate subkey for encrypting, as > opposed to creating one keypair that signs and encrypts. The example > I've seen around is that if you're set up the subkey way and the police > demand the priva

Re: Camellia

2008-06-13 Thread David Shaw
On Thu, Jun 12, 2008 at 01:38:16PM -0400, John W. Moore III wrote: > [EMAIL PROTECTED] wrote: > > > how hard would it be to write a patch for an option of > > --try-all-symmetrics > > or > > --use-symmetric-name > > that would ignore the cipher number and try all of them, > > or try only the one

Re: PGP doesn't import trust signatures w/ depth > 8 on keys exported with GPG

2008-06-13 Thread David Shaw
On Fri, Jun 13, 2008 at 11:35:08AM -0700, bezna wrote: > > Hi, > > I'm using PGP Desktop 9.8 and I noticed when I export a public key from GPG > and import it in PGP, any trust signatures made on it with GPG and given a > depth greater than 8 are lost. Presumably this is because of constraints >

Re: PGP doesn't import trust signatures w/ depth > 8 on keys exported with GPG

2008-06-13 Thread Robert J. Hansen
bezna wrote: > I was wondering if anyone can provide a rationalization for why this > is? This is the GnuPG-Users list, not PGP-Users. Generally speaking, we are not experts on the internal workings of PGP. You're better off asking PGP Corporation. _

PGP doesn't import trust signatures w/ depth > 8 on keys exported with GPG

2008-06-13 Thread bezna
Hi, I'm using PGP Desktop 9.8 and I noticed when I export a public key from GPG and import it in PGP, any trust signatures made on it with GPG and given a depth greater than 8 are lost. Presumably this is because of constraints within PGP, IE the maximum trust depth that can be set in PGP for a s

Re: Signatures stored as information inside a "public key"/certificate?

2008-06-13 Thread Morton D. Trace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 bezna wrote: > Hello, > > Which is correct? Are signatures an inherent part of the key or are they > stored extrinsically? > > > George i would put it this way, when I run gpg in command line mode I create a user ID and a secret key + a pub

Re: Signatures stored as information inside a "public key"/certificate?

2008-06-13 Thread Robert J. Hansen
bezna wrote: > I'm having a disagreement with someone over this. From what I've > read, signatures on a "public key" or rather, a certificate, > including the self-signature, are stored as a packet on that key. The > important point: This data (IE all the signatures made on your > certificate) is e

Re: Signatures stored as information inside a "public key"/certificate?

2008-06-13 Thread Werner Koch
On Fri, 13 Jun 2008 17:07, [EMAIL PROTECTED] said: > Which is correct? Are signatures an inherent part of the key or are they > stored extrinsically? Lets clarify the terms: - In OpenPGP parlance a "certificate" (as used with X.509) is called a "keyblock". It is perfectly okay to use the term

Signatures stored as information inside a "public key"/certificate?

2008-06-13 Thread bezna
Hello, I'm having a disagreement with someone over this. From what I've read, signatures on a "public key" or rather, a certificate, including the self-signature, are stored as a packet on that key. The important point: This data (IE all the signatures made on your certificate) is encoded on the