Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cr-gpg reports "bad signature" when the signature is in fact good #8

Open
dustinkirkland opened this issue Dec 29, 2011 · 5 comments
Open

Comments

@dustinkirkland
Copy link

I have email with good inline signatures, from trusted keys. I can save the original message from gmail to a text file, and GPG correctly detects that the message signature is good. cr-gpg, though, thinks the signature is "bad".

I'm happy to provide some examples, if that helps. But generically, I'm using the "bootmail" package from Ubuntu, which can be configured to automatically send a gpg-signed email message of log files when a machine boots.

Can anyone else confirm that inline signatures are, or aren't working with cr-gpg?

Thanks,
Dusitn

@RC1140
Copy link
Owner

RC1140 commented Dec 30, 2011

Hey Dustin

The inline signatures should be working , send me a copy of the 'bad signatures' and I'll have a look to see whats going wrong.

@dustinkirkland
Copy link
Author

On Fri, Dec 30, 2011 at 12:11 AM, Jameel Haffejee
reply@reply.github.com
wrote:

The inline signatures should be working , send me a copy of the 'bad signatures' and I'll have a look to see whats going wrong.

Sent privately.

:-Dustin

@RC1140
Copy link
Owner

RC1140 commented Jan 3, 2012

Thanks will check it out and let you know how it goes

@dustinkirkland
Copy link
Author

Any luck? Were you able to reproduce the issue at least?

@RC1140
Copy link
Owner

RC1140 commented Jan 9, 2012

Hi Dustin

I have not had the chance yet , but will let you as soon as I have something to report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants