Invalid selfsignature
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I just imported one of my public keys (after receiving it signed by other person), and when I was importing, I saw a message about "invalid self signature" for one of the UIDs. Is that serious? How could it happen? and... how can I solve it? Best Regards -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJLw+RuAAoJEMV4f6PvczxAPR4IAJlzibX1BY6RmocI0XArvL8p O2IxtXzuwx9mjWMWIZyRe5mRH3rinHDb5HYQP+7H+EctyhTOhqDUJATJhgCHCKJe S2vXhp2ODbevGCizvDQs92EvqdcDNRkGBHRC8eQRm/eeQ1AoekymmD7TZ8jTldyB 02roktlg3L24dSZtIMwZ6Esl5U214J/xbuAsAhF1uovLtJtOwLhaHOZegYontOYS ZRkVCWWDJi0rXu3w0H/QBMlkewTpXnNsMZ9Yx56qbpC30ymyDqtktNresQ+kfuX1 r5JciZ4E6fc/ESFBdkw0dYpH7vC29i0VgfP7LHcaq4dSWXMoFiK3MHCzD4Yy0V0= =1/qL -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Invalid Marker Packet issue using PGP to encrypt using GnuPG certificate
> On Apr 12, 2010, at 12:45 PM, Michael E. Strout wrote: > >> Hi all, >>We're using GnuPG to both create an asynchronous key pair, >> the public key of which we provide to clients, and to decrypt the files >> encrypted with that certificate after its been transfered. One particular >> client is uploading files which return an "Invalid Marker Packet" error when >> I try to decrypt them. >> >> I've tried installing the newest versions of gpg, but it doesn't matter >> whether I'm using 1.4.9 or 2.0.12, I get an "invalid marker packet" error. >> >> I've opened up an older upload which I was able to decrypt and the most >> recent upload in a hex editor and can see that the bytes following the PGP >> in the marker packet are different, >> >> i.e. the one in the old file is 50 47 50 c1 c0 4c which reads as P G P 193 >> 192 76 or PGP 12697676 or PGPÁÀL >> While the one in the new file is 50 47 50 C1 C1 4E which reads as P G P 193 >> 193 78 or PGP 12697934 or PGPÁÁN > > The only valid marker packet contains exactly 3 bytes: P, G, and P. Given > that the following byte is C1, it looks like that's the beginning of the next > packet, rather than part of the marker packet. C1 would be the encrypted > session key packet, which makes sense at that point in the document. > > Can you tell me a few bytes from *before* the P, G, P? Perhaps the length is > wrong. On Apr 12, 2010, at 6:07 PM, Michael E. Strout wrote: > Both Files begin with A8 03 50 47 50 A8 == Marker packet 03 == Length (3 bytes) 50 == 'P' 47 == 'G' 50 == 'P' That looks fine. It's possible there is corruption elsewhere in the file so that there is something that looks like a (mangled) marker packet, but this one is valid. I'd check into how the client is sending you the files. If they're using FTP, make sure they are sending in binary or image mode and not ascii or text mode. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Invalid Marker Packet issue using PGP to encrypt using GnuPG certificate
On Apr 12, 2010, at 12:45 PM, Michael E. Strout wrote: > Hi all, > We're using GnuPG to both create an asynchronous key pair, > the public key of which we provide to clients, and to decrypt the files > encrypted with that certificate after its been transfered. One particular > client is uploading files which return an "Invalid Marker Packet" error when > I try to decrypt them. > > I've tried installing the newest versions of gpg, but it doesn't matter > whether I'm using 1.4.9 or 2.0.12, I get an "invalid marker packet" error. > > I've opened up an older upload which I was able to decrypt and the most > recent upload in a hex editor and can see that the bytes following the PGP in > the marker packet are different, > > i.e. the one in the old file is 50 47 50 c1 c0 4c which reads as P G P 193 > 192 76 or PGP 12697676 or PGPÁÀL > While the one in the new file is 50 47 50 C1 C1 4E which reads as P G P 193 > 193 78 or PGP 12697934 or PGPÁÁN The only valid marker packet contains exactly 3 bytes: P, G, and P. Given that the following byte is C1, it looks like that's the beginning of the next packet, rather than part of the marker packet. C1 would be the encrypted session key packet, which makes sense at that point in the document. Can you tell me a few bytes from *before* the P, G, P? Perhaps the length is wrong. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Invalid Marker Packet issue using PGP to encrypt using GnuPG certificate
Hi all, We're using GnuPG to both create an asynchronous key pair, the public key of which we provide to clients, and to decrypt the files encrypted with that certificate after its been transfered. One particular client is uploading files which return an "Invalid Marker Packet" error when I try to decrypt them. I've tried installing the newest versions of gpg, but it doesn't matter whether I'm using 1.4.9 or 2.0.12, I get an "invalid marker packet" error. I've opened up an older upload which I was able to decrypt and the most recent upload in a hex editor and can see that the bytes following the PGP in the marker packet are different, i.e. the one in the old file is 50 47 50 c1 c0 4c which reads as P G P 193 192 76 or PGP 12697676 or PGPÁÀL While the one in the new file is 50 47 50 C1 C1 4E which reads as P G P 193 193 78 or PGP 12697934 or PGPÁÁN I figure the client is using PGP software (hence the marker packet) and may have upgraded their software since the last successfully decrypted upload, but I thought they could put anything they wanted in the marker packet and gpg would be fine... Has anyone else seen this and know of a way past it? ~Michael - CONFIDENTIALITY NOTICE - This e-mail message from ClearStructure Financial Technology, LLC is intended only for the individual or entity to which it is addressed. This e-mail may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you received this e-mail by accident, please notify the sender immediately and destroy this e-mail and all copies of it. We take steps to protect against viruses but advise you to carry out your own checks and precautions as we accept no liability for any which remain. We may monitor emails sent to and from our server(s) to ensure regulatory compliance to protect our clients and business. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: DRM -- digital rights management
On Apr 12, 2010, at 2:33 PM, M.B.Jr. wrote: > Hi, > I have this simple question (sorry for it), regarding "digital rights > management". > > As I understand, DRM in essence is the use of asymmetric cryptography, > which turns simple public keys into not-publicly-available public > keys. > > Is it correct? No. DRM is a collective term for the various means of controlling use of media in one way or another. It's possible to use asymmetric crypto as part of a DRM scheme, but this is not a requirement, or inherent in the idea of DRM. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
DRM -- digital rights management
Hi, I have this simple question (sorry for it), regarding "digital rights management". As I understand, DRM in essence is the use of asymmetric cryptography, which turns simple public keys into not-publicly-available public keys. Is it correct? Regards, Marcio Barbado, Jr. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
