Using subkeys to renew an expiring key

[SeidlS at schneider.com]

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> On 08/29/2006 04:36 PM, SeidlS at schneider.com wrote:
> > Your talking about document inbound to my process, encrypted by the
other
> > organizations.  That should work without an issue as you pointed out,
but
> > what about the outbound process?  In that instance we would be
encrypting
> > the file and sending it to the other organizations to be decrypted...
would
> > those orgainzations that haven't updated to the new key have problems
> > decrypting the file?
> This is a rather strange statement.
> Other organizations should have their OWN pubkeys to which documents
> sent to them are encrypted.
> - --
>

Good Point.  I wasn't thinking of that.  So for outbound documents, the
only issue that could exist would be verifying our signature if we are
signing the document?  Or is the signature part of the master key and
wouldn't be impacted by adding an additional subkey?

-Scott


>   Q.E.D.
> War is Peace
> Freedom is Slavery
> Ignorance is Strength
>
> ICQ UIN: 301825501
> OpenPGP key ID: 0x58D14EB3
> Key fingerprint: 00B9 3E17 630F F2A7 FF96  DA6B AEE0 EC27 58D1 4EB3
> Check fingerprints before trusting a key!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iD8DBQFE9F0AH+Dh0Dl5XacRA16VAJ9vwgPr/SQc2rMigKqUyxmJKDwOsQCfYN+e
> QvYTudheYNA74t8sY9ctY5k=
> =wEpX
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users