On Sun, Feb 19, 2012 at 08:16:32PM +, Paul Martin wrote:
> Some hints are here:
> http://ekaia.org/blog/2009/05/10/creating-new-gpgkey/
Also there's http://users.pepperfish.net/dsilvers/keysigcheck.sh which can help
you to check your options are right, by asking it to look for your
self-signat
I believe so. But to test, just try signing a file with
e.g. "gpg --clearsign", and check the hash at the top. It's also
possible to configure gpg to use different hashes, but in my
experience, it defaults to SHA2[56] with 4096 bit RSA with
current GnuPG versions.
Thanks, I have confirmed
Try http://wiki.debian.org/Keysigning/Offers :)
signature.asc
Description: This is a digitally signed message part.
On Sun, Feb 19, 2012 at 08:07:57PM +, peter green wrote:
> I have been encouraged to apply to become a debian developer by
> Steve McIntyre and Hector Oron.
>
> However before I can do so I need to get my GPG key signed by a
> couple of debian-developers.
>
> Also can someone confirm whether
On Sun, Feb 19, 2012 at 08:07:57PM +, peter green wrote:
> Also can someone confirm whether all 4096 bit RSA keys are "sha2
> capable" and if not how I check whether my key is "sha2" capable. I
> don't want to waste peoples time requesting signatures on a key that
> turns out to be unsuitable f
I have been encouraged to apply to become a debian developer by Steve
McIntyre and Hector Oron.
However before I can do so I need to get my GPG key signed by a couple
of debian-developers.
Also can someone confirm whether all 4096 bit RSA keys are "sha2
capable" and if not how I check whethe
6 matches
Mail list logo