Re: G83-6744 keyboard + smart-card reader
On Mon Jan 16, 2012 at 18:56:26 +, gn...@lists.grepular.com wrote: > I'm thinking of buying one of these keyboards with a built in smart card > reader: > > http://www.cherrycorp.com/english/keyboards/Security/Smart_Card_Keyboards/index.htm > > Which I understand is supported by GnuPG as per: > > http://www.gnupg.org/howtos/card-howto/en/smartcard-howto-single.html > > However, the place I'm planning on purchasing from: > > https://www.keyboardspecialists.co.uk/Shop/KBS/Product/2873/G83-6744/CherryG83-6744SmartBoard.aspx > > Has two different models: > > G83-6744LUAGB-2 > G83-6744LUZGB-2 > > And no explanation as to the difference. I've tried to contact their > support but haven't heared back yet. Does anyone have any experience of > this keyboard? Does anyone know what the slightly differing model > numbers mean? Am I right in assuming that they will *both* work fine > with GnuPG? > Looks to me like the only difference between both models is in their certifications. Maybe you want to take a look at the product page[1], where the following information is given in the models listing: G83-6744LUAGB-2 -> EMV 2000 Level 1 G83-6744LUZGB-2 -> EMV 2000 Level 1, Common Criteria EAL 3+ HTH. Cheers, Michael [1] http://www.cherry.de/cid/b2b_keyboards_SmartBoard_G83-6744.htm? -- - Michael Fladerer - GPG Key-ID: EE61F443 Key fingerprint: A56F FE73 5FCC 4FF1 2E72 360E ACE6 1874 EE61 F443 - ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Conflicting commands error?
On Tue Aug 23, 2011 at 09:51:59 -0400, michaelquig...@theway.org wrote: > Hello, > > I use this syntax to sign files in a script--it works without problems, > but when trying to manually sign a file, I'm receiving the following > result: > > > gpg --batch --armor -keyring /Publib/.../ARP_pubring.gpg > --secret-keyring /Prodlib/.../ARP_secring.gpg --local-user 55EC3D41\! > --output S0004458.asc --clear-sign S0004458 > gpg: conflicting commands > $ > > I'm sure I'm overlooking something simple, but I'm just not seeing it > today. > Try using --keyring instead of -keyring. Regards, Michael ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Creating signatures with expiration time
On Thu Apr 14, 2011 at 11:45:07 +0200, Jesus Cea wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 14/04/11 06:05, Daniel Kahn Gillmor wrote: > > On 04/13/2011 10:43 PM, Jesus Cea wrote: > >> My idea was to create a signature with a expiration date, so signatures > >> should be renewed every year. The OpenPGP Standard documents this type > >> of signature <http://tools.ietf.org/html/rfc4880#section-5.2.3.10>, but > >> GPG doesn't seems to have the option to create them. > > > > Look in the man pages for --default-cert-expire and --ask-cert-expire. > > > > If these do what you want, you can also set them in ~/.gnupg/gpg.conf so > > that you don't have to supply them on the command line every time. > > Thanks, Daniel. Looking the manual, I see "--default-sig-expire" and > "--ask-sig-expire" too. What is the difference with "cert"?. > > Maybe "cert" only ask for expiration when signing a key, while "sig" > always ask for an expiration for any kind of signature? > Sorry, I obviously missed the keyword 'data' in 'data signature' when I looked through the manpage. So dkg was right with --ask-cert-expire, which prompts for an expiration date of the signature you're going to perform. Michael -- - Michael Fladerer - GPG Key-ID: EE61F443 Key fingerprint: A56F FE73 5FCC 4FF1 2E72 360E ACE6 1874 EE61 F443 - ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Creating signatures with expiration time
On Thu Apr 14, 2011 at 00:05:18 -0400, Daniel Kahn Gillmor wrote: > On 04/13/2011 10:43 PM, Jesus Cea wrote: > > My idea was to create a signature with a expiration date, so signatures > > should be renewed every year. The OpenPGP Standard documents this type > > of signature <http://tools.ietf.org/html/rfc4880#section-5.2.3.10>, but > > GPG doesn't seems to have the option to create them. > > Look in the man pages for --default-cert-expire and --ask-cert-expire. > > If these do what you want, you can also set them in ~/.gnupg/gpg.conf so > that you don't have to supply them on the command line every time. > I guess --ask-sig-expire and --default-sig-expire is what you probably want to use, which you can define in your config, too. -- --------- Michael Fladerer - GPG Key-ID: EE61F443 Key fingerprint: A56F FE73 5FCC 4FF1 2E72 360E ACE6 1874 EE61 F443 - ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem with keyserver
On Wed Jan 26, 2011 at 17:13:22 -0500, Jerry wrote: > On Wed, 26 Jan 2011 16:21:26 -0500 > Daniel Kahn Gillmor articulated: > > > On 01/26/2011 01:14 PM, Jerry wrote: > > > Does anyone know if there is a problem with the following keyserver: > > > > > > hkp://keys.gnupg.net > > > > > > I have not been able to connect with it for several days now. > > > > keys.gnupg.net is a DNS round robin. > > > > if one of them fails, the other ones should be responsive at least. > > from my perspective on the network, i see: > > > > keys.gnupg.net. 86400 IN A > > 129.128.98.22 keys.gnupg.net. 86400 IN > > A 193.174.13.74 keys.gnupg.net. 86400 > > IN A 209.234.253.170 > > > > which are these machines: > > > > 129.128.98.22: pgp.srv.ualberta.ca. > > 193.174.13.74: pgpkeys.pca.dfn.de. > > 209.234.253.170: zimmermann.mayfirst.org. > > > > > > the last one (zimmermann.mayfirst.org, which i maintain) is functional > > for me, at least. > > > > the first one at least doesn't seem to be responsive at all right now, > > though :( > > > > you may also be interested in pool.sks-keyservers.net, which is > > updated automatically. > > Thanks, I have added that URL. Now, if I might ask a stupid question, > is there a specific port number that is used? I just want to make sure > my firewall is setup correctly. Presently I have it setup to allow any > port # for those URLs. I think it's the Horowitz Keyserver Protocol (hkp) which typically uses port 11371 (see [1]). [1] http://www.iana.org/assignments/port-numbers Michael ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Organizing groups of Keys
On Thu Nov 25, 2010 at 00:53:32 +1100, Ben McGinnes wrote: > On 24/11/10 10:35 PM, Aaron Berthold wrote: > > > Alternatively, is there a way to work with multiple-but-distinct > > keyrings without manually renaming the files and restarting the software > > when you want to switch? So I could have a keyring for work, one for > > study, etc. > > You can specify an additional keyring with the --keyring command, but > I believe that this is just an addition to the default keyring(s) and > not an override. The gpg manpage says: (...) --keyring file Add file to the current list of keyrings. (...) If the intent is to use the specified keyring alone, use --keyring along with --no-default-keyring. HTH. Cheers, Michael ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
