From dkg at fifthhorseman.net Thu Oct 1 00:00:50 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 30 Sep 2009 18:00:50 -0400
Subject: choosing an encryption target from a User ID
In-Reply-To: <200909302332.36254@thufir.ingo-kloecker.de>
References: <4AB90539.7020809@fifthhorseman.net> <200909292232.29640@thufir.ingo-kloecker.de> <4AC285DE.2050806@fifthhorseman.net>
<200909302332.36254@thufir.ingo-kloecker.de>
Message-ID: <4AC3D512.4060501@fifthhorseman.net>
On 09/30/2009 05:32 PM, Ingo Kl?cker wrote:
> Hmm, AFAIU, for someone who does not blindly certify such keys this
> shouldn't be a problem since those malicious keys wouldn't be valid and
> thus wouldn't take preference over a valid key ... unless somebody else
> this person trusts is trying to screw them.
The current gpg behavior is to use the first key with a matching User
ID, regardless of the validity of that User ID. So this causes (at
best) warnings and alerts about using an invalid key or (at worst) lets
someone with marginal ownertrust abuse the user by taking precedence
over a fully-trusted certification if the keyring happens to be ordered
in a certain way.
--dkg
PS i hear you about being paranoid and preferring to only trust my own
certifications. but the larger pool there is of people who understand
the two simple concepts, the more comfortable i am granting trusted
individuals marginal ownertrust, and taking advantage of the WoT to
verify identities i've yet to directly verify myself. It's way better
than trusting $DEITY-knows-who that comes pre-configured by default in
web browsers these days ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 891 bytes
Desc: OpenPGP digital signature
URL:
From kloecker at kde.org Thu Oct 1 00:21:54 2009
From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=)
Date: Thu, 01 Oct 2009 00:21:54 +0200
Subject: Decryption Fails on UserName but not on EmailAddress ???
In-Reply-To: <25661872.post@talk.nabble.com>
References: <25577787.post@talk.nabble.com> <25661872.post@talk.nabble.com>
Message-ID: <200910010021.55226@thufir.ingo-kloecker.de>
On Tuesday 29 September 2009, nschroth wrote:
> Interesting. The key is not listed twice, but...
>
> --list-keys PrimaryUserName shows ALL THREE keys while
> --list-keys PrimaryEmailAddress shows only the primary host key.
>
> Could it be that the name I used for the primary key was CompanyName
> and the email addresses for all the people had that as their domain
> (ex: Bill at companyname.com) ???
Makes sense.
gpg --list-keys foo
will list all keys where one of the user IDs contains the three
letters "foo" (substring match).
Please read the section "HOW TO SPECIFY A USER ID" in the manual page of
gpg (man gpg) for the different possibilities to specify what key(s) to
use for some operation with gpg.
Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL:
From ABrown at milbank.com Thu Oct 1 09:13:53 2009
From: ABrown at milbank.com (Brown, Annette)
Date: Thu, 1 Oct 2009 08:13:53 +0100
Subject: GPG Software
Message-ID: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
I wonder if you can help? One of our partners has had this loaded via
an e-mail he received and for some reason since it has been loaded the
search function on his Outlook has stopped working properly. Is there a
particular way in which to remove this software from his machine?
Many thanks.
Annette
_____________________________
Annette Brown | Milbank
10 Gresham Street | London | EC2V 7JD
T: +44 (0)20 7615 3132 | F: +44 (0)20 7615 3100
abrown at milbank.com | www.milbank.com
=======================================================================
IRS Circular 230 Disclosure: U.S. federal tax advice in the foregoing message from Milbank, Tweed, Hadley & McCloy LLP is not intended or written to be, and cannot be used, by any person for the purpose of avoiding tax penalties that may be imposed regarding the transactions or matters addressed. Some of that advice may have been written to support the promotion or marketing of the transactions or matters addressed within the meaning of IRS Circular 230, in which case you should seek advice based on your particular circumstances from an independent tax advisor.
=======================================================================
This e-mail message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From Michael.GRIFFITHS at arc-intl.com Fri Oct 2 12:24:02 2009
From: Michael.GRIFFITHS at arc-intl.com (michael GRIFFITHS)
Date: Fri, 2 Oct 2009 12:24:02 +0200
Subject: GPG Software
In-Reply-To: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
References: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
Message-ID: <6740B3A8EA1647478669675F861F16CF04FC2D7C@MAILFR1.emea.dmai.net>
Hi Annette,
First GPG wouldn't have been loaded on its own via email, this would
require user installation.
Which outlook version is he running? Also I am running outlook 2003 with
GPG installed and my search function works OK. How are they trying to do
a search?
Regards,
________________________________
Michael Griffiths - IT Systems Administrator
Direct dial: +44 (0) 113 2763422 | Office: +44 (0) 113 2710033 - Ext:
203 | Mobile: +44 (0) 788 1957504
Address: Arc House | Middleton Grove| Beeston | Leeds | LS11 5BX | UK
Email: michael.griffiths at arc-intl.com
P Please consider the environment before printing this email.
________________________________
________________________________
From: gnupg-users-bounces at gnupg.org
[mailto:gnupg-users-bounces at gnupg.org] On Behalf Of Brown, Annette
Sent: 01 October 2009 08:14
To: Gnupg-users at gnupg.org
Subject: GPG Software
I wonder if you can help? One of our partners has had this loaded via
an e-mail he received and for some reason since it has been loaded the
search function on his Outlook has stopped working properly. Is there a
particular way in which to remove this software from his machine?
Many thanks.
Annette
_____________________________
Annette Brown | Milbank
10 Gresham Street | London | EC2V 7JD
T: +44 (0)20 7615 3132 | F: +44 (0)20 7615 3100
abrown at milbank.com | www.milbank.com
=======================================================================
IRS Circular 230 Disclosure: U.S. federal tax advice in the foregoing
message from Milbank, Tweed, Hadley & McCloy LLP is not intended or
written to be, and cannot be used, by any person for the purpose of
avoiding tax penalties that may be imposed regarding the transactions or
matters addressed. Some of that advice may have been written to support
the promotion or marketing of the transactions or matters addressed
within the meaning of IRS Circular 230, in which case you should seek
advice based on your particular circumstances from an independent tax
advisor.
=======================================================================
This e-mail message may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), or the employee
or agent responsible for delivery of this message to the intended
recipient(s), you are hereby notified that any dissemination,
distribution or copying of this e-mail message is strictly prohibited.
If you have received this message in error, please immediately notify
the sender and delete this e-mail message from your computer.
To ensure an optimal service, the ARC INTERNATIONAL Group uses the most powerful antiviruses and antispam systems currently available. This message and any attachments (the "message") are intended solely for the addresses and are confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accordance with its purpose, any dissemination or disclosure, either in whole or in part, is prohibited without formal approval. The internet cannot guarantee the integrity of this message; ARC INTERNATIONAL (and its subsidiaries) shall (will) not therefore be liable for the message if modified.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From Michael.GRIFFITHS at arc-intl.com Fri Oct 2 12:26:54 2009
From: Michael.GRIFFITHS at arc-intl.com (michael GRIFFITHS)
Date: Fri, 2 Oct 2009 12:26:54 +0200
Subject: GPG Software
In-Reply-To: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
References: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
Message-ID: <6740B3A8EA1647478669675F861F16CF04FC2D7E@MAILFR1.emea.dmai.net>
Sorry I forgot to actually answer your question.
It will appear under the add/remove programs. For windows it will most
likely be named "GnuPG for windows"
________________________________
Michael Griffiths - IT Systems Administrator
Direct dial: +44 (0) 113 2763422 | Office: +44 (0) 113 2710033 - Ext:
203 | Mobile: +44 (0) 788 1957504
Address: Arc House | Middleton Grove| Beeston | Leeds | LS11 5BX | UK
Email: michael.griffiths at arc-intl.com
P Please consider the environment before printing this email.
________________________________
________________________________
From: gnupg-users-bounces at gnupg.org
[mailto:gnupg-users-bounces at gnupg.org] On Behalf Of Brown, Annette
Sent: 01 October 2009 08:14
To: Gnupg-users at gnupg.org
Subject: GPG Software
I wonder if you can help? One of our partners has had this loaded via
an e-mail he received and for some reason since it has been loaded the
search function on his Outlook has stopped working properly. Is there a
particular way in which to remove this software from his machine?
Many thanks.
Annette
_____________________________
Annette Brown | Milbank
10 Gresham Street | London | EC2V 7JD
T: +44 (0)20 7615 3132 | F: +44 (0)20 7615 3100
abrown at milbank.com | www.milbank.com
=======================================================================
IRS Circular 230 Disclosure: U.S. federal tax advice in the foregoing
message from Milbank, Tweed, Hadley & McCloy LLP is not intended or
written to be, and cannot be used, by any person for the purpose of
avoiding tax penalties that may be imposed regarding the transactions or
matters addressed. Some of that advice may have been written to support
the promotion or marketing of the transactions or matters addressed
within the meaning of IRS Circular 230, in which case you should seek
advice based on your particular circumstances from an independent tax
advisor.
=======================================================================
This e-mail message may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), or the employee
or agent responsible for delivery of this message to the intended
recipient(s), you are hereby notified that any dissemination,
distribution or copying of this e-mail message is strictly prohibited.
If you have received this message in error, please immediately notify
the sender and delete this e-mail message from your computer.
To ensure an optimal service, the ARC INTERNATIONAL Group uses the most powerful antiviruses and antispam systems currently available. This message and any attachments (the "message") are intended solely for the addresses and are confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accordance with its purpose, any dissemination or disclosure, either in whole or in part, is prohibited without formal approval. The internet cannot guarantee the integrity of this message; ARC INTERNATIONAL (and its subsidiaries) shall (will) not therefore be liable for the message if modified.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jmoore3rd at bellsouth.net Fri Oct 2 12:40:28 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Fri, 02 Oct 2009 06:40:28 -0400
Subject: GPG Software
In-Reply-To: <6740B3A8EA1647478669675F861F16CF04FC2D7E@MAILFR1.emea.dmai.net>
References: <7252B42E1ACBB64ABAE3F0D82E0FC7DE03DE78EC@exln1.milbank.local>
<6740B3A8EA1647478669675F861F16CF04FC2D7E@MAILFR1.emea.dmai.net>
Message-ID: <4AC5D89C.5010208@bellsouth.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
michael GRIFFITHS wrote:
> Sorry I forgot to actually answer your question.
> It will appear under the add/remove programs. For windows it will most
> likely be named ?GnuPG for windows?
IIRC, it will appear under Add/Remove Programs as GPGOL. [GPG /for/
Outlook]
JOHN ;)
Timestamp: Friday 02 Oct 2009, 06:40 --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Public Key at: http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: http://www.gswot.org
Comment: Personal Web Page: http://tinyurl.com/yzhbhx
iQEcBAEBCgAGBQJKxdiaAAoJEBCGy9eAtCsPbxgH/1nWTl0gQz7xtpluar+mQgDd
p0bxpR/f1crSt6Uwy2jOOa2cK+N4Qmj66skfxy25uUlkVcblhGoi+ISj75J+wF2J
MjAMMNlME6Z9cJgXZXNfZclwzXbCV0/qCn3VzwZybWmrKXIywlV+AZ4o3g/pYYfc
sjGmYKs5ejZ9zKsSFBI02+6rPBttKLFxEjXO98890J8GA9tXNtxk28jxy98T13/6
os/4zdl+R1J0brqLJZFRsHswGeKuvCdENEnoU7wXekPq1lCuTeKCkvifIpSH++6W
3l88gGgoXivS48YBU2go2VkhrC3LA/RS6VRGudQFCBUoaeQhzVAEYXo7utPoMuw=
=NIqC
-----END PGP SIGNATURE-----
From kloecker at kde.org Fri Oct 2 21:12:36 2009
From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=)
Date: Fri, 02 Oct 2009 21:12:36 +0200
Subject: choosing an encryption target from a User ID
In-Reply-To: <4AC3D512.4060501@fifthhorseman.net>
References: <4AB90539.7020809@fifthhorseman.net>
<200909302332.36254@thufir.ingo-kloecker.de>
<4AC3D512.4060501@fifthhorseman.net>
Message-ID: <200910022112.36733@thufir.ingo-kloecker.de>
On Thursday 01 October 2009, Daniel Kahn Gillmor wrote:
> On 09/30/2009 05:32 PM, Ingo Kl?cker wrote:
> > Hmm, AFAIU, for someone who does not blindly certify such keys this
> > shouldn't be a problem since those malicious keys wouldn't be valid
> > and thus wouldn't take preference over a valid key ... unless
> > somebody else this person trusts is trying to screw them.
>
> The current gpg behavior is to use the first key with a matching User
> ID, regardless of the validity of that User ID. So this causes (at
> best) warnings and alerts about using an invalid key or (at worst)
> lets someone with marginal ownertrust abuse the user by taking
> precedence over a fully-trusted certification if the keyring happens
> to be ordered in a certain way.
Indeed. That's a weird policy.
Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL:
From tux.tsndcb at free.fr Fri Oct 2 23:05:04 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Fri, 2 Oct 2009 23:05:04 +0200 (CEST)
Subject: poldi logon screen
In-Reply-To: <1097098412.7302011254170178164.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1884120112.8057441254517504436.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi,
I answer to my self, in fact it's an gdm setup.
Best Regards.
----- Mail Original -----
De: "tux tsndcb"
?: gnupg-users at gnupg.org
Envoy?: Lundi 28 Septembre 2009 22h36:18 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: poldi logon screen
Hi all,
This is the last functionnaly than I've to setup.
I'm on debian squeeze with limpam-poldi 0.4.1-2, I can logon with my smartcard, so poldi is ok, but I've the normal debian logon screen, not the poldi screen like this :
http://www.g10code.com/graphics/poldi-screenshot-gdm.png
So my question, how to have this logon screen ?
Thanks in advanced for your answer.
Best Regards.
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
From talmage at orange.zero.jp Sun Oct 4 12:36:34 2009
From: talmage at orange.zero.jp (Talmage)
Date: Sun, 4 Oct 2009 19:36:34 +0900
Subject: OpenPGP-Card2.0 and Omnikey Cardman 3021?
In-Reply-To: <874oqk5xy8.fsf@vigenere.g10code.de>
References: <6539A033-8048-4CEC-830A-1819D410CE8E@orange.zero.jp>
<874oqk5xy8.fsf@vigenere.g10code.de>
Message-ID:
Werner, thanks for the response.
I figured it was a problem with the Omnikey, so I went ahead and got a
SCR335, only to find out that it gives the same exact error when
generating keys on the card... I'm starting to wonder if this is some
kind of USB issue with Mac OS Snow Leopard.
My system is a Mac OS X 10.6 system, with gnupg 1.4.10, and
OpenPGPCard v2.0.
I read somewhere that the SCR335 needs the newest firmware, so updated
firmware to 5.23, but still the same problem.
Again, here is the output.
Any clues as to what might be causing this?
Has anyone successfully used the OpenPGPCard v2.0 on Snow Leopard?
Thanks.
Talmage
--------------------------------
$ gpg --version
gpg (GnuPG) 1.4.10
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128,
CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$ gpg --card-edit
Application ID ...: D27600012401020000050000012E0000
Version ..........: 2.0
Manufacturer .....: ZeitControl
Serial number ....: 0000012E
Name of cardholder: Test User
Language prefs ...: en
Sex ..............: unspecified
URL of public key : [not set]
Login data .......: [not set]
Private DO 1 .....: [not set]
Private DO 2 .....: [not set]
Signature PIN ....: not forced
Key attributes ...: 2048R 2048R 2048R
Max. PIN lengths .: 32 32 32
PIN retry counter : 3 0 3
Signature counter : 0
Signature key ....: [none]
Encryption key....: [none]
Authentication key: [none]
General key info..: [none]
Command> admin
Admin commands are allowed
Command> generate
Make off-card backup of encryption key? (Y/n) n
Please enter the PIN
What keysize do you want for the Signature key? (2048)
What keysize do you want for the Encryption key? (2048)
What keysize do you want for the Authentication key? (2048)
Please specify how long the key should be valid.
0 = key does not expire
= key expires in n days
w = key expires in n weeks
m = key expires in n months
y = key expires in n years
Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y
You need a user ID to identify your key; the software constructs the
user ID
from the Real Name, Comment and Email Address in this form:
"Heinrich Heine (Der Dichter) "
Real name: Test User
Email address: test at domain
Comment: TEST2
You selected this USER-ID:
"Test User (TEST2) "
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
gpg: generating new key
gpg: 3 Admin PIN attempts remaining before card is permanently locked
Please enter the Admin PIN
gpg: please wait while key is being generated ...
gpg: ccid_transceive failed: (0x1000a)
gpg: apdu_send_simple(0) failed: card I/O error
gpg: generating key failed
gpg: key generation failed: general error
Key generation failed: general error
Command> quit
$ gpg --card-status --debug-ccid-driver
gpg: DBG: ccid-driver: using CCID reader 0
(ID=04E6:5115:21120713300395:0)
gpg: DBG: ccid-driver: idVendor: 04E6 idProduct: 5115 bcdDevice: 0523
gpg: DBG: ccid-driver: ChipCard Interface Descriptor:
gpg: DBG: ccid-driver: bLength 54
gpg: DBG: ccid-driver: bDescriptorType 33
gpg: DBG: ccid-driver: bcdCCID 1.10 (Warning: Only
accurate for version 1.0)
gpg: DBG: ccid-driver: nMaxSlotIndex 0
gpg: DBG: ccid-driver: bVoltageSupport 1 5.0V
gpg: DBG: ccid-driver: dwProtocols 3 T=0 T=1
gpg: DBG: ccid-driver: dwDefaultClock 4000
gpg: DBG: ccid-driver: dwMaxiumumClock 8000
gpg: DBG: ccid-driver: bNumClockSupported 0
gpg: DBG: ccid-driver: dwDataRate 10753 bps
gpg: DBG: ccid-driver: dwMaxDataRate 344105 bps
gpg: DBG: ccid-driver: bNumDataRatesSupp. 0
gpg: DBG: ccid-driver: dwMaxIFSD 252
gpg: DBG: ccid-driver: dwSyncProtocols 00000000
gpg: DBG: ccid-driver: dwMechanical 00000000
gpg: DBG: ccid-driver: dwFeatures 000100BA
gpg: DBG: ccid-driver: Auto configuration based on ATR
gpg: DBG: ccid-driver: Auto voltage selection
gpg: DBG: ccid-driver: Auto clock change
gpg: DBG: ccid-driver: Auto baud rate change
gpg: DBG: ccid-driver: Auto PPS made by CCID
gpg: DBG: ccid-driver: TPDU level exchange
gpg: DBG: ccid-driver: dwMaxCCIDMsgLen 271
gpg: DBG: ccid-driver: bClassGetResponse echo
gpg: DBG: ccid-driver: bClassEnvelope echo
gpg: DBG: ccid-driver: wlcdLayout none
gpg: DBG: ccid-driver: bPINSupport 0
gpg: DBG: ccid-driver: bMaxCCIDBusySlots 1
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOn:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bPowerSelect ......: 0x00 (auto)
gpg: DBG: ccid-driver: [0008] 00 00
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 21
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: [0010] 3B DA 18 FF 81 B1
gpg: DBG: ccid-driver: [0016] FE 75 1F 03 00 31 C5 73 C0 01 40 00
90 00 0C
gpg: DBG: ccid-driver: PC_to_RDR_GetParameters:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 2
gpg: DBG: ccid-driver: [0007] 00 00 00
gpg: DBG: ccid-driver: RDR_to_PC_Parameters:
gpg: DBG: ccid-driver: dwLength ..........: 7
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 2
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: protocol ..........: T=1
gpg: DBG: ccid-driver: bmFindexDindex ....: 11
gpg: DBG: ccid-driver: bmTCCKST1 .........: 10
gpg: DBG: ccid-driver: bGuardTimeT1 ......: 00
gpg: DBG: ccid-driver: bmWaitingIntegersT1: 75
gpg: DBG: ccid-driver: bClockStop ........: 00
gpg: DBG: ccid-driver: bIFSC .............: 254
gpg: DBG: ccid-driver: bNadValue .........: 0
gpg: DBG: ccid-driver: PC_to_RDR_SetParameters:
gpg: DBG: ccid-driver: dwLength ..........: 7
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bProtocolNum ......: 0x01
gpg: DBG: ccid-driver: [0008] 00 00 11 10 00 75 00 FE
gpg: DBG: ccid-driver: [0016] 00
gpg: DBG: ccid-driver: RDR_to_PC_Parameters:
gpg: DBG: ccid-driver: dwLength ..........: 7
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: protocol ..........: T=1
gpg: DBG: ccid-driver: bmFindexDindex ....: 11
gpg: DBG: ccid-driver: bmTCCKST1 .........: 10
gpg: DBG: ccid-driver: bGuardTimeT1 ......: 00
gpg: DBG: ccid-driver: bmWaitingIntegersT1: 75
gpg: DBG: ccid-driver: bClockStop ........: 00
gpg: DBG: ccid-driver: bIFSC .............: 254
gpg: DBG: ccid-driver: bNadValue .........: 0
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 5
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: bBWI ..............: 0x00
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 C1 01 FC 3C
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 5
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: [0010] 00 E1 01 FC 1C
gpg: DBG: ccid-driver: IFSD has been set to 252
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 15
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 5
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 0B 00 A4 04
gpg: DBG: ccid-driver: [0016] 00 06 D2 76 00 01 24 01 2D
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 6
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 5
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 02 90 00 92gpg: DBG: ccid-
driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 6
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 4F 00 C0
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 22
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 6
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 12 D2 76 00
gpg: DBG: ccid-driver: [0016] 01 24 01 02 00 00 05 00 00 01 2E 00
00 90 00 6Agpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 7
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 5F
gpg: DBG: ccid-driver: [0016] 52 00 C2
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 16
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 7
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 0C 00 31 C5
gpg: DBG: ccid-driver: [0016] 73 C0 01 40 05 90 00 90 00 0F
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 8
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] C4 00 4B
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 13
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 8
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 09 01 20 20
gpg: DBG: ccid-driver: [0016] 20 03 00 03 90 00 F8
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 9
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 6E 00 A1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 223
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 9
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 DB 4F 10 D2
gpg: DBG: ccid-driver: [0016] 76 00 01 24 01 02 00 00 05 00 00 01
2E 00 00 5F
gpg: DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00
73 81 B7 C0
gpg: DBG: ccid-driver: [0048] 0A 7C 00 08 00 08 00 08 00 08 00 C1
06 01 08 00
gpg: DBG: ccid-driver: [0064] 00 20 00 C2 06 01 08 00 00 20 00 C3
06 01 08 00
gpg: DBG: ccid-driver: [0080] 00 20 00 C4 07 01 20 20 20 03 00 03
C5 3C 00 00
gpg: DBG: ccid-driver: [0096] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0112] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0128] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0144] 00 00 00 00 00 00 00 00 00 00 C6 3C
00 00 00 00
gpg: DBG: ccid-driver: [0160] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0176] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0192] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0208] 00 00 00 00 00 00 00 00 CD 0C 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0224] 00 00 00 00 00 00 90 00 14
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 10
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 5E 00 D1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 6
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 10
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 02 90 00 D2gpg: DBG: ccid-
driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 11
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 6E 00 A1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 223
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 11
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 DB 4F 10 D2
gpg: DBG: ccid-driver: [0016] 76 00 01 24 01 02 00 00 05 00 00 01
2E 00 00 5F
gpg: DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00
73 81 B7 C0
gpg: DBG: ccid-driver: [0048] 0A 7C 00 08 00 08 00 08 00 08 00 C1
06 01 08 00
gpg: DBG: ccid-driver: [0064] 00 20 00 C2 06 01 08 00 00 20 00 C3
06 01 08 00
gpg: DBG: ccid-driver: [0080] 00 20 00 C4 07 01 20 20 20 03 00 03
C5 3C 00 00
gpg: DBG: ccid-driver: [0096] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0112] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0128] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0144] 00 00 00 00 00 00 00 00 00 00 C6 3C
00 00 00 00
gpg: DBG: ccid-driver: [0160] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0176] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0192] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0208] 00 00 00 00 00 00 00 00 CD 0C 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0224] 00 00 00 00 00 00 90 00 14
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 12
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 6E 00 E1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 223
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 12
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 DB 4F 10 D2
gpg: DBG: ccid-driver: [0016] 76 00 01 24 01 02 00 00 05 00 00 01
2E 00 00 5F
gpg: DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00
73 81 B7 C0
gpg: DBG: ccid-driver: [0048] 0A 7C 00 08 00 08 00 08 00 08 00 C1
06 01 08 00
gpg: DBG: ccid-driver: [0064] 00 20 00 C2 06 01 08 00 00 20 00 C3
06 01 08 00
gpg: DBG: ccid-driver: [0080] 00 20 00 C4 07 01 20 20 20 03 00 03
C5 3C 00 00
gpg: DBG: ccid-driver: [0096] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0112] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0128] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0144] 00 00 00 00 00 00 00 00 00 00 C6 3C
00 00 00 00
gpg: DBG: ccid-driver: [0160] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0176] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0192] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0208] 00 00 00 00 00 00 00 00 CD 0C 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0224] 00 00 00 00 00 00 90 00 54
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 13
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 6E 00 A1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 223
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 13
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 DB 4F 10 D2
gpg: DBG: ccid-driver: [0016] 76 00 01 24 01 02 00 00 05 00 00 01
2E 00 00 5F
gpg: DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00
73 81 B7 C0
gpg: DBG: ccid-driver: [0048] 0A 7C 00 08 00 08 00 08 00 08 00 C1
06 01 08 00
gpg: DBG: ccid-driver: [0064] 00 20 00 C2 06 01 08 00 00 20 00 C3
06 01 08 00
gpg: DBG: ccid-driver: [0080] 00 20 00 C4 07 01 20 20 20 03 00 03
C5 3C 00 00
gpg: DBG: ccid-driver: [0096] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0112] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0128] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0144] 00 00 00 00 00 00 00 00 00 00 C6 3C
00 00 00 00
gpg: DBG: ccid-driver: [0160] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0176] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0192] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0208] 00 00 00 00 00 00 00 00 CD 0C 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0224] 00 00 00 00 00 00 90 00 14
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 14
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 65 00 EA
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 27
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 14
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 17 5B 0A 55
gpg: DBG: ccid-driver: [0016] 73 65 72 3C 3C 54 65 73 74 5F 2D 02
65 6E 5F 35
gpg: DBG: ccid-driver: [0032] 01 39 90 00 B8
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 15
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 5F
gpg: DBG: ccid-driver: [0016] 50 00 C0
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 6
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 15
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 02 90 00 92gpg: DBG: ccid-
driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 16
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 6E 00 E1
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 223
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 16
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 DB 4F 10 D2
gpg: DBG: ccid-driver: [0016] 76 00 01 24 01 02 00 00 05 00 00 01
2E 00 00 5F
gpg: DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00
73 81 B7 C0
gpg: DBG: ccid-driver: [0048] 0A 7C 00 08 00 08 00 08 00 08 00 C1
06 01 08 00
gpg: DBG: ccid-driver: [0064] 00 20 00 C2 06 01 08 00 00 20 00 C3
06 01 08 00
gpg: DBG: ccid-driver: [0080] 00 20 00 C4 07 01 20 20 20 03 00 03
C5 3C 00 00
gpg: DBG: ccid-driver: [0096] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0112] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0128] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0144] 00 00 00 00 00 00 00 00 00 00 C6 3C
00 00 00 00
gpg: DBG: ccid-driver: [0160] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0176] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0192] 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0208] 00 00 00 00 00 00 00 00 CD 0C 00 00
00 00 00 00
gpg: DBG: ccid-driver: [0224] 00 00 00 00 00 00 90 00 54
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 17
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 00
gpg: DBG: ccid-driver: [0016] C4 00 0B
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 13
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 17
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 09 01 20 20
gpg: DBG: ccid-driver: [0016] 20 03 00 03 90 00 B8
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 18
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 00
gpg: DBG: ccid-driver: [0016] 7A 00 F5
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 11
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 18
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 07 93 03 00
gpg: DBG: ccid-driver: [0016] 00 00 90 00 47
gpg: DBG: ccid-driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 19
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 00 05 00 CA 01
gpg: DBG: ccid-driver: [0016] 01 00 CF
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 6
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 19
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 00 02 90 00 92gpg: DBG: ccid-
driver: PC_to_RDR_XfrBlock:
gpg: DBG: ccid-driver: dwLength ..........: 9
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 20
gpg: DBG: ccid-driver: bBWI ..............: 0x04
gpg: DBG: ccid-driver: wLevelParameter ...: 0x0000
gpg: DBG: ccid-driver: [0010] 00 40 05 00 CA 01
gpg: DBG: ccid-driver: [0016] 02 00 8C
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 6
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 20
gpg: DBG: ccid-driver: bStatus ...........: 0
gpg: DBG: ccid-driver: bChainParameter ...: 0x04
gpg: DBG: ccid-driver: [0010] 00 40 02 90 00 D2Application ID ...:
D27600012401020000050000012E0000
Version ..........: 2.0
Manufacturer .....: ZeitControl
Serial number ....: 0000012E
Name of cardholder: Test User
Language prefs ...: en
Sex ..............: unspecified
URL of public key : [not set]
Login data .......: [not set]
Private DO 1 .....: [not set]
Private DO 2 .....: [not set]
Signature PIN ....: not forced
Key attributes ...: 2048R 2048R 2048R
Max. PIN lengths .: 32 32 32
PIN retry counter : 3 0 3
Signature counter : 0
Signature key ....: [none]
Encryption key....: [none]
Authentication key: [none]
General key info..: [none]
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOff:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 21
gpg: DBG: ccid-driver: [0007] 00 00 00
gpg: DBG: ccid-driver: RDR_to_PC_SlotStatus:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 21
gpg: DBG: ccid-driver: bStatus ...........: 1
gpg: DBG: ccid-driver: bClockStatus ......: 0x01 (stopped-L)
-----------------------------
On Sep 30, 2009, at 11:06 PM, Werner Koch wrote:
> On Wed, 30 Sep 2009 13:51, talmage at orange.zero.jp said:
>
>> Has anyone gotten the Omnikey Cardman 3021 to work with the internal
>> drivers?
>
> That one does not work reliable with 2048 bit keys. The Windows
> driver
> seems to have a workaround for it and I tried to come up with a
> similar
> workaround. However the protocol analysis I did is not complete and
> we
> often get out of sync. Avoid Omnikey or ask them to explain how to
> correctly switch and operation in TPDU mode.
>
>
> Salam-Shalom,
>
> Werner
>
> --
> Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
>
From tux.tsndcb at free.fr Sun Oct 4 17:51:18 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Sun, 4 Oct 2009 17:51:18 +0200 (CEST)
Subject: Is it possible to have the same authentication key on several
smartcard ?
In-Reply-To: <409331006.8198641254671410277.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1866389316.8199091254671478154.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi Werner,
How to generated an authentication key off-card ?
Because when I generate it by :
gpg2 --edit-key
commande > addkey
RSA (sign only)
and make a keytocard to authentication, it's appears on sign key (S) and not authentication key (A) .
Thanks in advanced for your answer.
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Jeudi 24 Septembre 2009 23h01:46 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi werner,
I think I've the solution, could you confirm it please :
gpg2 --edit-key
commande > addkey
RSA (sign only)
Thanks in advanced for your answer
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Jeudi 24 Septembre 2009 22h44:01 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi Werner,
Sorry, but I've need more informations about it.
I tried this :
gpg2 --edit-key
commande > genkey => commande invalide , may be you wanted to say addkey ?, but in this case what choice : RSA (sign only) or RSA (encrypt only) ?
Thanks in advanced for these informations and your answer.
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Mercredi 23 Septembre 2009 14h45:37 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi Werner,
Many thanks for your answer, I will try it.
Best Regard
----- Mail Original -----
De: "Werner Koch"
?: "tux tsndcb"
Cc: gnupg-users at gnupg.org
Envoy?: Mercredi 23 Septembre 2009 13h36:49 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: Is it possible to have the same authentication key on several smartcard ?
On Wed, 23 Sep 2009 11:46, tux.tsndcb at free.fr said:
> Is it possible to have the same authentication key on several smartcard ?
Yes. You need to generate the key off-card and and then put it onto the
card. Use gpg --edit-key and the subcommands genkey and keytocard for
this.
> Is it possible to done an authentication key backup when it has been generated directly on a smartcard ?
No. An on-card generated key can't be extracted from the card (except
for the public part of course).
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
From tux.tsndcb at free.fr Sun Oct 4 22:25:20 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Sun, 4 Oct 2009 22:25:20 +0200 (CEST)
Subject: Is it possible to have the same authentication key on several
smartcard ?
In-Reply-To: <1866389316.8199091254671478154.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <905051996.8237171254687920639.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi Werner,
I answer to my self, in fact I need to use the expert mode to do that, sorry ...
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Dimanche 4 Octobre 2009 17h51:18 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi Werner,
How to generated an authentication key off-card ?
Because when I generate it by :
gpg2 --edit-key
commande > addkey
RSA (sign only)
and make a keytocard to authentication, it's appears on sign key (S) and not authentication key (A) .
Thanks in advanced for your answer.
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Jeudi 24 Septembre 2009 23h01:46 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi werner,
I think I've the solution, could you confirm it please :
gpg2 --edit-key
commande > addkey
RSA (sign only)
Thanks in advanced for your answer
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Jeudi 24 Septembre 2009 22h44:01 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi Werner,
Sorry, but I've need more informations about it.
I tried this :
gpg2 --edit-key
commande > genkey => commande invalide , may be you wanted to say addkey ?, but in this case what choice : RSA (sign only) or RSA (encrypt only) ?
Thanks in advanced for these informations and your answer.
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Mercredi 23 Septembre 2009 14h45:37 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Is it possible to have the same authentication key on several smartcard ?
Hi Werner,
Many thanks for your answer, I will try it.
Best Regard
----- Mail Original -----
De: "Werner Koch"
?: "tux tsndcb"
Cc: gnupg-users at gnupg.org
Envoy?: Mercredi 23 Septembre 2009 13h36:49 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: Is it possible to have the same authentication key on several smartcard ?
On Wed, 23 Sep 2009 11:46, tux.tsndcb at free.fr said:
> Is it possible to have the same authentication key on several smartcard ?
Yes. You need to generate the key off-card and and then put it onto the
card. Use gpg --edit-key and the subcommands genkey and keytocard for
this.
> Is it possible to done an authentication key backup when it has been generated directly on a smartcard ?
No. An on-card generated key can't be extracted from the card (except
for the public part of course).
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
From simon at josefsson.org Mon Oct 5 08:52:48 2009
From: simon at josefsson.org (Simon Josefsson)
Date: Mon, 05 Oct 2009 08:52:48 +0200
Subject: SHA2 in OpenPGP cards?
In-Reply-To: <87my4e56cn.fsf@vigenere.g10code.de> (Werner Koch's message of
"Tue, 29 Sep 2009 13:38:00 +0200")
References: <87y6nykxbr.fsf@mocca.josefsson.org>
<87my4e56cn.fsf@vigenere.g10code.de>
Message-ID: <8763aubadb.fsf@mocca.josefsson.org>
Werner Koch writes:
> On Tue, 29 Sep 2009 09:46, simon at josefsson.org said:
>> Hi! Before I spend time testing it, can the OpenPGP card support
>> RSA-SHA2 signatures?
>
> The v2 cards support any hash agorithm as long as they fit into pkcs#1.
When I attempt to generate a new key on the card with this in my
~/.gnupg/gpg.conf:
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
I get this error:
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
gpg: checking created signature failed: Bad signature
gpg: signing failed: Bad signature
gpg: make_keysig_packet failed: Bad signature
Key generation failed: Bad signature
When I comment out the three lines above, it worked fine. Any ideas?
GnuPG 2.0.13 from Debian.
/Simon
From JCochran at hearstnp.com Sat Oct 3 00:50:26 2009
From: JCochran at hearstnp.com (Cochran, Jason L)
Date: Fri, 2 Oct 2009 17:50:26 -0500
Subject: PHP Script
Message-ID:
http://www.phpclasses.org/browse/package/245.html
I got this working with the above code.
~ Jason
Midland Reporter Telegram
Direct: (432) 687-9011 (x 3111)
www.mywesttexas.com
From: Cochran, Jason L
Sent: Friday, October 02, 2009 5:21 PM
To: 'gnupg-users at gnupg.org'
Subject: PHP Script
I need help getting a scrip working. I am hosted with Hostgator. My key
is in the cpanel. Yet I can't get php to work with it.
PHP_INFO: http://gator1028.hostgator.com/~mwtadmin/php_info.php
SCRIPT: http://gator1028.hostgator.com/~mwtadmin/pgp_test.php
Thanks!
===== pgp_test.php =====
~ Jason
Midland Reporter Telegram
Direct: (432) 687-9011 (x 3111)
www.mywesttexas.com
========================================================
This e-mail message is intended only for the personal
use of the recipient(s) named above. If you are not
an intended recipient, you may not review, copy or
distribute this message.
If you have received this communication in error, please
notify the sender immediately by e-mail and delete the original message.
========================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From JCochran at hearstnp.com Sat Oct 3 00:21:13 2009
From: JCochran at hearstnp.com (Cochran, Jason L)
Date: Fri, 2 Oct 2009 17:21:13 -0500
Subject: PHP Script
Message-ID:
I need help getting a scrip working. I am hosted with Hostgator. My key
is in the cpanel. Yet I can't get php to work with it.
PHP_INFO: http://gator1028.hostgator.com/~mwtadmin/php_info.php
SCRIPT: http://gator1028.hostgator.com/~mwtadmin/pgp_test.php
Thanks!
===== pgp_test.php =====
~ Jason
Midland Reporter Telegram
Direct: (432) 687-9011 (x 3111)
www.mywesttexas.com
========================================================
This e-mail message is intended only for the personal
use of the recipient(s) named above. If you are not
an intended recipient, you may not review, copy or
distribute this message.
If you have received this communication in error, please
notify the sender immediately by e-mail and delete the original message.
========================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jaylstein at yahoo.com Mon Oct 5 09:59:13 2009
From: jaylstein at yahoo.com (jason stein)
Date: Mon, 5 Oct 2009 00:59:13 -0700 (PDT)
Subject: configuring gpg to be executed via cgi
Message-ID: <349034.30628.qm@web38106.mail.mud.yahoo.com>
What steps must be taken to execute gpg from a ( perl ) web app?? For this instance we will say we are using apache web server software.
?
Thanks
j
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From simon at josefsson.org Mon Oct 5 15:54:37 2009
From: simon at josefsson.org (Simon Josefsson)
Date: Mon, 05 Oct 2009 15:54:37 +0200
Subject: SSH using OpenPGP card under Windows
Message-ID: <87hbuegd42.fsf@mocca.josefsson.org>
Has anyone managed to get this combination working?
There is a Putty extension but is appears to be non-free:
http://smartcard-auth.de/ssh-en.html
There is a free smartcard-enabled Putty:
http://www.joebar.ch/puttysc/
But it requires a PKCS#11 module -- I see on scute.org that
it is possible to build for Windows, but are there any
pre-compiled binaries available?
There seems to be some efforts in the OpenSC project to facilitate this,
but there is also documentation that suggests smartcard with putty
doesn't work perfectly.
Thanks,
/Simon
From ddurant at intevaproducts.com Mon Oct 5 18:07:52 2009
From: ddurant at intevaproducts.com (Durant, Dean)
Date: Mon, 5 Oct 2009 16:07:52 +0000
Subject: beginner type questions
Message-ID: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
Hello, I noticed, on windows (which I truly despise), when I type
C:\Documents and Settings\me\Application Data\gnupg>gpg --gen-key
I get:
gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc. (add'l copyleft info)
Please select what kind of key you want:
(1) RSA and RSA (default)
(2) DSA and Elgamal
(3) DSA (sign only)
(4) RSA (sign only)
on ubuntu, I get these choices (the version of GPG is 2.0.9):
Please select what kind of key you want:
(1) DSA and Elgamal (default)
(2) DSA (sign only)
(5) RSA (sign only)
What is the difference? Isn't RSA better?
I tried using apt-get to get the version on linux up to the same version # on windows, and it wouldn't.
Once you generate a key, is it bound to the email address supplied during generation, so that, if someone else emails your key out, you won't be able to decrypt something encrypted to their email? Or is the email address completely uninvolved?
Thanks, Dean
From rjh at sixdemonbag.org Mon Oct 5 19:54:41 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Mon, 05 Oct 2009 13:54:41 -0400
Subject: beginner type questions
In-Reply-To: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
References: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
Message-ID: <4ACA32E1.7000803@sixdemonbag.org>
Durant, Dean wrote:
> What is the difference? Isn't RSA better?
The differences are irrelevant to the overwhelming majority of users.
Arguments about whether RSA or DSA are better pop up from time to time.
These arguments have always struck me as being kind of like arguing
over whether Godzilla or King Kong is better at urban destruction.
Maybe you like Godzilla, maybe I like King Kong, but at the end of the
day either one of them will get the job done in style.
> I tried using apt-get to get the version on linux up to the same
> version # on windows, and it wouldn't.
This is expected. New versions of GnuPG are being released all the
time. Most releases offer very, /very/ small improvements over what
came before. Ubuntu keeps track of what's changed in GnuPG since 2.0.9
was released. If something major was added or a security bug was fixed,
Ubuntu will modify their version of GnuPG appropriately. Otherwise,
Ubuntu's policy is generally, "wait until late October for Karmic Koala
to come out, and that will have the latest version of everything you want."
> Or is the email address completely uninvolved?
Uninvolved. The email addresses exist to make the keys easier for human
beings to use. By and large, the computer doesn't use the User ID at
all. :)
From jmoore3rd at bellsouth.net Mon Oct 5 22:02:35 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Mon, 05 Oct 2009 16:02:35 -0400
Subject: beginner type questions
In-Reply-To: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
References: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
Message-ID: <4ACA50DB.2000004@bellsouth.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Durant, Dean wrote:
> Hello, I noticed, on windows (which I truly despise), when I type
>
> C:\Documents and Settings\me\Application Data\gnupg>gpg --gen-key
>
> I get:
>
> gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc. (add'l copyleft info)
>
> Please select what kind of key you want:
> (1) RSA and RSA (default)
> (2) DSA and Elgamal
> (3) DSA (sign only)
> (4) RSA (sign only)
>
> on ubuntu, I get these choices (the version of GPG is 2.0.9):
> Please select what kind of key you want:
>
> (1) DSA and Elgamal (default)
> (2) DSA (sign only)
> (5) RSA (sign only)
>
> What is the difference? Isn't RSA better?
Robert's answer was accurate but I'm not sure it was the answer to the
question You were asking. Between versions 2.0.9 & 2.0.12 the Default
for Key Generation was changed. This change is viewed as minor by many
which apparently includes the Ubuntu developers. :)
The reason the Default was changed was to make better use of available
Hash functions. DSA Signing Keys are limited to 160bit Hashes unless
DSA2 is invoked, RSA Signing Keys can utilize all the Hash functions
without any 'games' being played. To eliminate any confusion in the
future and based upon the number of folks who eventually migrated away
from DSA Keys to RSA Keys due to personal perceptions the Default was
changed to RSA.
Additionally, in the very beginning RSA was encumbered by patents which
have now expired. You can easily work around this in Ubuntu at present
by selecting option 5 and then generating an RSA Encryption sub-Key.
HTH
JOHN ;)
Timestamp: Monday 05 Oct 2009, 16:02 --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Public Key at: http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: http://www.gswot.org
Comment: Personal Web Page: http://tinyurl.com/yzhbhx
iQEcBAEBCgAGBQJKylDaAAoJEBCGy9eAtCsPdPgIAI/SfIwVc2RVR8I8lhBcem8s
vJzcAz+gZ41vH0afLPRo3RbUmJbxhkzX2qxPZ8w8mH4csTSIAfCtdlG9h+sqXWK/
HB8Hxxk1zVahPSqHo8i5PT//cSM1SMES5K5dw9dFZrCO0IcQZwy81MDxJt6sw7cK
mxCO89fZVC1PpPgh352jWh1DUKqvQ1K5hok8zAzvQvdKimWfoG7K2sRXMuvDfn30
6F6+kWCGEzM3C+oMqEhLXAqhQl1FCfv4slyfmZUhHLc8Q30RJy3R4gIYpigVl0h0
pP5ZQy01SqklRBxg1naWBx/rVAUuWYdIiKnGXPVNf11GLA7mOMsZVIzXni6HYXU=
=ycQz
-----END PGP SIGNATURE-----
From rjh at sixdemonbag.org Mon Oct 5 23:33:38 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Mon, 05 Oct 2009 17:33:38 -0400
Subject: email hashes in PGP keys as protection against spam
In-Reply-To: <200910052302.40020.mailinglisten@hauke-laging.de>
References: <200910050409.00014.mailinglisten@hauke-laging.de> <200910052027.01509.mailinglisten@hauke-laging.de> <4ACA45A2.6020702@sixdemonbag.org>
<200910052302.40020.mailinglisten@hauke-laging.de>
Message-ID: <4ACA6632.3000405@sixdemonbag.org>
Hauke Laging wrote:
> Maybe. But I would not call it science that you imply that harvesting
> from key servers will result in about the same amount of spam as pure
> address guessing by the spammers would.
Estimating how many email addresses are released to spammers via the
keyservers is a black art. It has been attempted, though. See, e.g.,
John Clizbe's result.
For your proposal to work, you can never have an email address exposed.
Ever. Anywhere. The instant you screw up and your email address gets
out, the game is over. Soon a spammer will discover it. Within days
all the spammers will have it, since spammers share email lists with
each other.
In the end, you haven't done anything to stop spam. All you've done is
bought yourself a little time, and paid a very high price for it --
you've made it very difficult for people who want to talk to you to get
in touch with you.
> Your point maybe. It seems a bit strange to me that you believe to be
> capable of calculating everyone's personal spam risk.
Objective reality is the same for everybody. The objective reality of
the situation is that as soon as your email address gets exposed
anywhere, spammers will get it. Closing off just one avenue of address
collection is absurd; it's like facing a horde of army ants and thinking
that just by stomping on one you're going to do something about the swarm.
> Because you want to decide for others what risks they have to take
> and which not. You may make fun of afraid flight passengers but
> nonetheless such assessments should be up to the user.
It already _is_ up to the user. Nobody forces you to put an email
address on your key. You can leave it off if you want. If you're
really that concerned about keyserver spam, then feel free. Be my
guest. The protocol accommodates you.
But I think it's a very bad idea to start changing the protocol just to
appease the phantom fears of a small number of users. Once you do that,
then everyone who has a phantom fear will demand the protocol be changed
to support them.
> Snake-oil refers to fooling somebody. I don't do that.
You may be fooling yourself.
I have cc'd GnuPG-Users on this one. There doesn't appear to be
anything in this thread that's related to ongoing GnuPG development, so
continuing it on -devel seems inappropriate. Let's move it over there.
From wk at gnupg.org Tue Oct 6 10:01:58 2009
From: wk at gnupg.org (Werner Koch)
Date: Tue, 06 Oct 2009 10:01:58 +0200
Subject: SSH using OpenPGP card under Windows
In-Reply-To: <87hbuegd42.fsf@mocca.josefsson.org> (Simon Josefsson's message
of "Mon, 05 Oct 2009 15:54:37 +0200")
References: <87hbuegd42.fsf@mocca.josefsson.org>
Message-ID: <877hv9rlvt.fsf@vigenere.g10code.de>
On Mon, 5 Oct 2009 15:54, simon at josefsson.org said:
> But it requires a PKCS#11 module -- I see on scute.org that
> it is possible to build for Windows, but are there any
> pre-compiled binaries available?
Scute is part of gpg4win 2.0.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From wk at gnupg.org Tue Oct 6 10:04:10 2009
From: wk at gnupg.org (Werner Koch)
Date: Tue, 06 Oct 2009 10:04:10 +0200
Subject: SSH using OpenPGP card under Windows
In-Reply-To: <87hbuegd42.fsf@mocca.josefsson.org> (Simon Josefsson's message
of "Mon, 05 Oct 2009 15:54:37 +0200")
References: <87hbuegd42.fsf@mocca.josefsson.org>
Message-ID: <873a5xrls5.fsf@vigenere.g10code.de>
On Mon, 5 Oct 2009 15:54, simon at josefsson.org said:
> There is a free smartcard-enabled Putty:
> http://www.joebar.ch/puttysc/
I had in mind to change putty to optionally support gpg-agent - much the
same as we do under Unix. However I had not enough time to work on it.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From simon at josefsson.org Tue Oct 6 10:44:19 2009
From: simon at josefsson.org (Simon Josefsson)
Date: Tue, 06 Oct 2009 10:44:19 +0200
Subject: SSH using OpenPGP card under Windows
In-Reply-To: <877hv9rlvt.fsf@vigenere.g10code.de> (Werner Koch's message of
"Tue, 06 Oct 2009 10:01:58 +0200")
References: <87hbuegd42.fsf@mocca.josefsson.org>
<877hv9rlvt.fsf@vigenere.g10code.de>
Message-ID: <87zl84ewt8.fsf@mocca.josefsson.org>
Werner Koch writes:
> On Mon, 5 Oct 2009 15:54, simon at josefsson.org said:
>
>> But it requires a PKCS#11 module -- I see on scute.org that
>> it is possible to build for Windows, but are there any
>> pre-compiled binaries available?
>
> Scute is part of gpg4win 2.0.
Great.
I'm trying to use it with PuttySC's 'pprint' and it says:
scute-assuan[2756]: can't create socket: Function not implemented
scute-assuan[2756]: can't create socket: Function not implemented
sc: C_initialize failed
Running gpg-agent says it is running and available. Running 'gpg
--card-status' works. Any ideas?
/Simon
From abolukoumiuas24601 at gmail.com Tue Oct 6 15:24:56 2009
From: abolukoumiuas24601 at gmail.com (Reva Dicerbo)
Date: Tue, 6 Oct 2009 17:24:56 +0400
Subject: illegal porn, preteen boys, preteen pussy, young nymphets, preteen
sex!
Message-ID: <255eaff50910060624i39377a36vb33a4eb15ece3c4@mail.gmail.com>
http://adultsexkey.com/vids/part01/
http://adultsexkey.com/vids/part02/
http://adultsexkey.com/vids/part03/
http://adultsexkey.com/vids/part04/
http://adultsexkey.com/vids/part05/
http://adultsexkey.com/vids/part06/
http://adultsexkey.com/vids/part07/
http://adultsexkey.com/vids/part08/
http://adultsexkey.com/vids/part09/
http://adultsexkey.com/vids/part10/
illegal porn
illegal cp
illegal young girls
illegal lolita
illegal girls
illegal preteen
lolitas illegal
illegal pedo
very little girls, illegal cp
illegal pussy
pre lolita illegal lolitas
illegal lolitas
illegal preteens
illegal preteen sex
illegal street racing
illegal pedo kids
illegal child porn
illegal loli
illegal teens
underage bbs illegal lolitas
preteen boys
nude preteen boys
preteen boys in underwear
gay preteen boys
preteen boys sex
preteen boys nude
preteen boys penis
little preteen boys in underwear
naked preteen boys
preteen boys masturbating
preteen gay boys
preteen boys russian
galleries of preteen boys in underwear
preteen nude boys
preteen gay boys sex
preteen boys in speedos
young gay boys preteen sex
young gay preteen boys
tiny preteen lolitas and boys
preteen boys erect penis
preteen pussy
young preteen pussy
preteen lolita pussy
preteen pussy pics
preteen pussies
young lolita preteen underage, underage pussy
preteen pedo pussy
illegal preteen pussy
tight preteen pussy
best preteen pussy
preteen girls pussy
free preteen pussy
pussy preteen
free underage dog pussy preteen
preteen shaved pussy
preteen model pussy
hairless preteen pussy
men fucking preteen pussy
wet preteen pussy
bald preteen pussy
young nymphets
young nymphets art
really young nymphets
young nymphets art young nymphet
free young nymphets galleries
young naked nymphets
nymphets young nymphets
young nude nymphets
hot young nymphets
nymphets young
very young nymphets
free young nymphets lolitas girl ass
free young nude nymphets galleries
young nymphets nude
young teen nymphets
young nymphets art, young nymphet
young nymphets galleries
young nymphets lolita
young nymphets, nymphets
wild young nymphets
preteen sex
preteen lolita sex
preteen sex stories
illegal preteen sex
preteen girl sex
preteen underage sex
preteen boy and girl sex
preteen sex pics
preteen boys sex
preteen lolitas having sex
child sex preteen lolita
russian preteen sex
preteen sex, illegal sex
preteen sex videos
young preteen blonde sex
preteen boy sex
preteen gay boys sex
preteen russian sex
young gay boys preteen sex
preteen ukraine sex
From tux.tsndcb at free.fr Thu Oct 8 19:46:18 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Thu, 8 Oct 2009 19:46:18 +0200 (CEST)
Subject: How to enable the reader's keypad
In-Reply-To: <260434015.8967331255022686060.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1390349622.8969821255023978322.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi,
I'm using gnupg2 2.0.13 (with libccid on my debian) and a smardcard reader with keypad, but code PIN is always ask on my desktop, not on the reader.
On my scdaemon.conf I've not disable-keypad
So how to do this ?
Thanks in advanced for your answer.
Best regards
From David.Gray at turpin-distribution.com Fri Oct 9 13:47:07 2009
From: David.Gray at turpin-distribution.com (David Gray)
Date: Fri, 9 Oct 2009 12:47:07 +0100
Subject: Testing the exit status
Message-ID: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
Hi,
Does GPG return different status codes when it exits?
I'm specifically looking for different types of error, such
as file not found, key not found, invalid passphrase etc.
I'm using the Windows version if that makes any difference.
Rgds
Dave
Registered Office: Turpin Distribution Services Ltd, Pegasus Drive, Stratton Business Park, Biggleswade, Bedfordshire, SG18 8TQ, UK. ***** Registered in England No. 1331778 ***** This email may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorised use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.
From awingnut at hotmail.com Fri Oct 9 17:40:39 2009
From: awingnut at hotmail.com (gw1500se)
Date: Fri, 9 Oct 2009 08:40:39 -0700 (PDT)
Subject: Network Mounted Home Directory and removal of --passphrase option
In-Reply-To: <87ab0irnpj.fsf@vigenere.g10code.de>
References: <25510161.post@talk.nabble.com>
<87ab0irnpj.fsf@vigenere.g10code.de>
Message-ID: <25823176.post@talk.nabble.com>
Werner Koch wrote:
>
>
> Well, it is available for 6 years and GnuPG 2.0 was released 3 years
> ago. Gpg-agent is not optional but a cornerstone of GnuPG-2.
>
> To let us help you fixing your installation, you should give us a bit
> more detailed information and exact error messages.
>
>
> Salam-Shalom,
>
> Werner
>
Thanks for the reply. I admit I am behind but as there were no problems
there was no real need to change GPG.
As I said in the original message I believe the problem is associated with
the way the agent determines the path for the .gnupg directory if the user's
home is auto-mounted via Open Directory.
The specific error is:
gpg-agent[6675]: error binding socket to
'/Network/Servers/xxxxxx.xxxxxxxx.com/Volumes/USER1/Users-home/xxxxxxx/.gnupg/S.gpg-agent':
Operation not supported
While that path is perfectly valid ($HOME) I have never been able to get it
to work with anything for unknown reasons. The path that I believe would
work is '/Volumes/USER1/Users-home/xxxxxxx/.gnupg/S.gpg-agent'. However,
the best path would be ~xxxxxxx/.gnupg/S.gpg-agent'.
--
View this message in context: http://www.nabble.com/Network-Mounted-Home-Directory-and-removal-of---passphrase-option-tp25510161p25823176.html
Sent from the GnuPG - User mailing list archive at Nabble.com.
From wk at gnupg.org Sat Oct 10 16:14:09 2009
From: wk at gnupg.org (Werner Koch)
Date: Sat, 10 Oct 2009 16:14:09 +0200
Subject: Testing the exit status
In-Reply-To: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
(David Gray's message of "Fri, 9 Oct 2009 12:47:07 +0100")
References: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
Message-ID: <87ws33qqtq.fsf@vigenere.g10code.de>
On Fri, 9 Oct 2009 13:47, David.Gray at turpin-distribution.com said:
> Does GPG return different status codes when it exits?
> I'm specifically looking for different types of error, such
> as file not found, key not found, invalid passphrase etc.
This would not be reliable. There are just too many stati to map them
to exit codes. What you need to do is to use the status lines
(--status-fd N) - or just go with gpgme.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From hs2412 at gmail.com Sat Oct 10 19:37:48 2009
From: hs2412 at gmail.com (Hardeep Singh)
Date: Sat, 10 Oct 2009 23:07:48 +0530
Subject: beginner type questions
In-Reply-To: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
References: <4FA18C2881FC5E4F8F6BF89B8C9919360286B4DE72@MBX1.EXCHPROD.USA.NET>
Message-ID:
try gpg --gen-key --expert
Hardeep Singh
http://blog.Hardeep.name
On Mon, Oct 5, 2009 at 9:37 PM, Durant, Dean wrote:
> Hello, I noticed, on windows (which I truly despise), when I type
>
> C:\Documents and Settings\me\Application Data\gnupg>gpg --gen-key
>
> I get:
>
> gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc. (add'l copyleft info)
>
> Please select what kind of key you want:
> ? (1) RSA and RSA (default)
> ? (2) DSA and Elgamal
> ? (3) DSA (sign only)
> ? (4) RSA (sign only)
>
> on ubuntu, I get these choices (the version of GPG is 2.0.9):
> Please select what kind of key you want:
>
> (1) DSA and Elgamal (default)
> (2) DSA (sign only)
> (5) RSA (sign only)
>
> What is the difference? ? Isn't RSA better?
>
> I tried using apt-get to get the version on linux up to the same version # on windows, and it wouldn't.
>
> Once you generate a key, is it bound to the email address supplied during generation, so that, if someone else emails your key out, you won't be able to decrypt something encrypted to their email? ? Or is the email address completely uninvolved?
>
> Thanks, Dean
>
>
>
>
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>
From mcse83 at hotmail.com Sun Oct 11 15:37:46 2009
From: mcse83 at hotmail.com (Sean Wilson)
Date: Sun, 11 Oct 2009 14:37:46 +0100
Subject: OpenPGP error
Message-ID:
Why is it when I sign an email and someone replies to it I sometimes get
the following error:
Part of the message signed; click on 'Details' button for more information
in the details it says:
OpenPGP Security Info
Error - signature verification failed
gpg command line and output:
C:\Program Files\GNU\GnuPG\gpg.exe
gpg: Signature made 10/11/09 14:13:48 using RSA key ID xxxxxx
gpg: BAD signature from "Sean Wilson "
Why does this happen?
If I send an email between two different email accounts and I sign it,
then reply I NEVER get a broken signature so why does this happen when
other people reply to my emails?
Thank you!
From mlisten at hammernoch.net Sun Oct 11 16:01:13 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Sun, 11 Oct 2009 16:01:13 +0200
Subject: OpenPGP error
In-Reply-To:
References:
Message-ID: <4AD1E529.7050506@hammernoch.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Sean Wilson wrote on 11.10.09 15:37:
> Why is it when I sign an email and someone replies to it I sometimes get
> the following error:
>
> Part of the message signed; click on 'Details' button for more information
>
> in the details it says:
>
> OpenPGP Security Info
>
> Error - signature verification failed
>
> gpg command line and output:
> C:\Program Files\GNU\GnuPG\gpg.exe
> gpg: Signature made 10/11/09 14:13:48 using RSA key ID xxxxxx
> gpg: BAD signature from "Sean Wilson "
>
> Why does this happen?
>
> If I send an email between two different email accounts and I sign it,
> then reply I NEVER get a broken signature so why does this happen when
> other people reply to my emails?
You're using in-line signatures, the recipient does not use gnupg and
cites your mail when replying, isn't it?
In this case, the following is happening: he/she is citing your mail
including the signature. Enigmail tries to verify it, but due to the
insertion of citation marks, e.g. "> " at the beginning of the lines,
your original message is modified, so the signature is broken.
It doesn't make much sense to sign messages to recipients who can't
verify it. If your recipient is using enigmail, it will strip your
signature upon replying.
HTH
Ludwig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBCgAGBQJK0eUpAAoJEA52XAUJWdLjC8gIALAF4b60P9EPwVTq1REeKZLU
ULBvDraFRktopbmNuQCFNgf7k7qApzUgumkxyu9Wzq0dQKnv76jBcbQfkM3sYUKJ
jxTBGj3rSy1ybfiWfPLVr89Ed0q9LdQvLVgkRLeGYjNqbdEcSfm7x45Xxkzkk5c6
Buyxy5iGtrljZUo9wV6q4pRN+fGbHsAT42OCOFKKlEN2y6EC0OxL29AQTO42uX7N
WjL1/wW0f/H8tUDw8+vlB94TUANNxsHTr30mVTx3KejNZOehnyPv6N9GS3+BrP55
GkMHTu4xZRFVWS2n/IYg2LI5c0xQuocfHimpLBnZ7KMBqwNycXRJzSQocaeJ4CQ=
=X52Z
-----END PGP SIGNATURE-----
From jmoore3rd at bellsouth.net Sun Oct 11 18:11:20 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Sun, 11 Oct 2009 12:11:20 -0400
Subject: OpenPGP error
In-Reply-To:
References:
Message-ID: <4AD203A8.4040204@bellsouth.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Sean Wilson wrote:
> Why is it when I sign an email and someone replies to it I sometimes get
> the following error:
>
> Part of the message signed; click on 'Details' button for more information
>
> in the details it says:
>
> OpenPGP Security Info
>
> Error - signature verification failed
>
> gpg command line and output:
> C:\Program Files\GNU\GnuPG\gpg.exe
> gpg: Signature made 10/11/09 14:13:48 using RSA key ID xxxxxx
> gpg: BAD signature from "Sean Wilson "
>
> Why does this happen?
Oftentimes, the individual replying to You uses a Mail Client that
doesn't strip off Your prior Signature armor block and neither do they
do so manually. [far too many folks _never_ clean their replies]
When GPG encounters the Signature Block embedded in the Reply it
'stumbles' and refuses to verify it.
JOHN ;)
Timestamp: Sunday 11 Oct 2009, 12:11 --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Public Key at: http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: http://www.gswot.org
Comment: Personal Web Page: http://tinyurl.com/yzhbhx
iQEcBAEBCgAGBQJK0gOnAAoJEBCGy9eAtCsPsUoH/0vs3euBSVeaS+ytnOgmeNDX
ASFIJumjGVixY2ZCopW4iIvcCfwSxe5v/fd39OHlfBorb7Vprjh3rdGRLIcei3hk
f2LS6fTXC7ffXZ0+Xh3QAXxB1LjHNupC0uUFVud4Z/OKp5kPScH0kwivQucXyp3c
t//wYfGH6OcxyiJRnEpvHLG7dKAB857Myg4pfCI6zWL3Bq0vma46ECJ1Wap5KaWv
lOzDXCTwlesr6OSmxzw78ygf+Bf1eynQ+C7GaS+DK0YNrbSgeiJgq25rUt9b/6rt
c9OKaaKbMI7y84KqZluqND8YhapyPCe6fI/x3hWtUs4E8Slaq42dvSkzSCCkuKA=
=sgcA
-----END PGP SIGNATURE-----
From jdever at triad.rr.com Mon Oct 12 05:50:58 2009
From: jdever at triad.rr.com (Jim Dever)
Date: Sun, 11 Oct 2009 23:50:58 -0400
Subject: Key types
Message-ID: <4AD2A7A2.60201@triad.rr.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Just a quick question:
Are there any caveats I should be aware of if I generate an RSA signing
key with an Elgamal encryption subkey?
- --
Jim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
iEYEAREDAAYFAkrSp6IACgkQygKI8gBpGS4Q4gCg1KwqAjmj4yR9SBJF1e38bx/r
MOMAoPyXi2OAPJWC4KgQ+pSt8wPj1Ry1
=PMyc
-----END PGP SIGNATURE-----
From rjh at sixdemonbag.org Mon Oct 12 07:39:11 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Mon, 12 Oct 2009 01:39:11 -0400
Subject: Key types
In-Reply-To: <4AD2A7A2.60201@triad.rr.com>
References: <4AD2A7A2.60201@triad.rr.com>
Message-ID: <4AD2C0FF.902@sixdemonbag.org>
Jim Dever wrote:
> Are there any caveats I should be aware of if I generate an RSA
> signing key with an Elgamal encryption subkey?
No.
From David.Gray at turpin-distribution.com Mon Oct 12 11:29:00 2009
From: David.Gray at turpin-distribution.com (David Gray)
Date: Mon, 12 Oct 2009 10:29:00 +0100
Subject: Testing the exit status
In-Reply-To: <87ws33qqtq.fsf@vigenere.g10code.de>
References: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
<87ws33qqtq.fsf@vigenere.g10code.de>
Message-ID: <33CE89420E3A834A82E48C2C747A7061029239AF@HERMES.turpin-bg.local>
Hi,
Thanks for the input.
Can you tell me what the numeric arguments are for status-fd?
I've downloaded the source for GPG and looked at the doc/DETAILS
file but on Windows this is unreadable.
Also it seems as if gpgme is not available for Windows, is this correct?
I'm running GPG from a C# application using the Process class. If I
understand
correctly then you are suggesting I use status-fd to redirect to a file
and then
open this to interrogate the results.
Thanks & regards
Dave
-----Original Message-----
From: Werner Koch [mailto:wk at gnupg.org]
Sent: 10 October 2009 15:14
To: David Gray
Cc: gnupg-users at gnupg.org
Subject: Re: Testing the exit status
On Fri, 9 Oct 2009 13:47, David.Gray at turpin-distribution.com said:
> Does GPG return different status codes when it exits?
> I'm specifically looking for different types of error, such
> as file not found, key not found, invalid passphrase etc.
This would not be reliable. There are just too many stati to map them
to exit codes. What you need to do is to use the status lines
(--status-fd N) - or just go with gpgme.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
Registered Office: Turpin Distribution Services Ltd, Pegasus Drive, Stratton Business Park, Biggleswade, Bedfordshire, SG18 8TQ, UK. ***** Registered in England No. 1331778 ***** This email may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorised use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.
From David.Gray at turpin-distribution.com Mon Oct 12 11:56:40 2009
From: David.Gray at turpin-distribution.com (David Gray)
Date: Mon, 12 Oct 2009 10:56:40 +0100
Subject: gpgme on Windows
Message-ID: <33CE89420E3A834A82E48C2C747A7061029239B1@HERMES.turpin-bg.local>
Hi all,
Been doing some searching this morning to see if gpgme is available for
Windows and can be used commercially. Is anyone using this product on
Windows
under .net 3.5 (C#) that can give advice?
Also does anyone know where the Windows download site is?
Thanks in advance
Dave
Registered Office: Turpin Distribution Services Ltd, Pegasus Drive, Stratton Business Park, Biggleswade, Bedfordshire, SG18 8TQ, UK. ***** Registered in England No. 1331778 ***** This email may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorised use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.
From wk at gnupg.org Mon Oct 12 11:59:40 2009
From: wk at gnupg.org (Werner Koch)
Date: Mon, 12 Oct 2009 11:59:40 +0200
Subject: Testing the exit status
In-Reply-To: <33CE89420E3A834A82E48C2C747A7061029239AF@HERMES.turpin-bg.local>
(David Gray's message of "Mon, 12 Oct 2009 10:29:00 +0100")
References: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
<87ws33qqtq.fsf@vigenere.g10code.de>
<33CE89420E3A834A82E48C2C747A7061029239AF@HERMES.turpin-bg.local>
Message-ID: <87zl7xorub.fsf@vigenere.g10code.de>
On Mon, 12 Oct 2009 11:29, David.Gray at turpin-distribution.com said:
> Can you tell me what the numeric arguments are for status-fd?
That is the file descriptor obn which output should happen. Usualy you
woul use
--status-fd 2
to output to stderr; however how can use arbitrary file descriptors.
> I've downloaded the source for GPG and looked at the doc/DETAILS
> file but on Windows this is unreadable.
Read it in an editor (e.g. notepad). As with all code we use Unix line
endings (LF) and not Windows line endings (CR,LF).
> Also it seems as if gpgme is not available for Windows, is this correct?
It is available for Windows. Simply install gpg4win (the light version
is sufficient) and you find the gpgme dll in the install directory.
libgpgme-11.dll is the native one, libgpgme-glib-11.dll is the one to
use with GLIB based software and libgpgme-qt-11.dll the one to use with
QT based software. Note that the file gpgme-w32spawn.exe must be in the
same directory as the DLL. The header file is identical for Unix and
Windows, a manual is online at
http://gnupg.org/documentation/manuals.en.html .
> I'm running GPG from a C# application using the Process class. If I
> understand
There is a C# wrapper for GPGME as well, please use a search machine to
locate it.
> correctly then you are suggesting I use status-fd to redirect to a file
> and then
> open this to interrogate the results.
No, you need to use pipes for that.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From dshaw at jabberwocky.com Mon Oct 12 14:26:46 2009
From: dshaw at jabberwocky.com (David Shaw)
Date: Mon, 12 Oct 2009 08:26:46 -0400
Subject: Key types
In-Reply-To: <4AD2A7A2.60201@triad.rr.com>
References: <4AD2A7A2.60201@triad.rr.com>
Message-ID:
On Oct 11, 2009, at 11:50 PM, Jim Dever wrote:
> Just a quick question:
>
> Are there any caveats I should be aware of if I generate an RSA
> signing
> key with an Elgamal encryption subkey?
No caveats. In fact, my own key is exactly that.
David
From ciprian.craciun at gmail.com Mon Oct 12 13:58:04 2009
From: ciprian.craciun at gmail.com (Ciprian Dorin, Craciun)
Date: Mon, 12 Oct 2009 14:58:04 +0300
Subject: gpg-agent --daemon running in foreground
Message-ID: <8e04b5820910120458o10f91a2ex8ad0f1361b96dd9d@mail.gmail.com>
Hello all!
I'm facing the following problem: I need to run gpg-agent, but
without him going into background. Is there any solution to this one?
Thanks,
Ciprian.
From dshaw at jabberwocky.com Mon Oct 12 15:08:50 2009
From: dshaw at jabberwocky.com (David Shaw)
Date: Mon, 12 Oct 2009 09:08:50 -0400
Subject: gpg-agent --daemon running in foreground
In-Reply-To: <8e04b5820910120458o10f91a2ex8ad0f1361b96dd9d@mail.gmail.com>
References: <8e04b5820910120458o10f91a2ex8ad0f1361b96dd9d@mail.gmail.com>
Message-ID:
On Oct 12, 2009, at 7:58 AM, Ciprian Dorin, Craciun wrote:
> Hello all!
>
> I'm facing the following problem: I need to run gpg-agent, but
> without him going into background. Is there any solution to this one?
I'm not sure exactly what you're trying to do, but you can run gpg-
agent without it backgrounding by leaving off the "--daemon" option.
David
From ciprian.craciun at gmail.com Mon Oct 12 15:57:49 2009
From: ciprian.craciun at gmail.com (Ciprian Dorin, Craciun)
Date: Mon, 12 Oct 2009 16:57:49 +0300
Subject: gpg-agent --daemon running in foreground
In-Reply-To:
References: <8e04b5820910120458o10f91a2ex8ad0f1361b96dd9d@mail.gmail.com>
Message-ID: <8e04b5820910120657i580249a9v2a46f7233be2738@mail.gmail.com>
On Mon, Oct 12, 2009 at 4:08 PM, David Shaw wrote:
> On Oct 12, 2009, at 7:58 AM, Ciprian Dorin, Craciun wrote:
>
>> ? Hello all!
>>
>> ? I'm facing the following problem: I need to run gpg-agent, but
>> without him going into background. Is there any solution to this one?
>
> I'm not sure exactly what you're trying to do, but you can run gpg-agent
> without it backgrounding by leaving off the "--daemon" option.
>
> David
So I have the following situation: I want to be able to run
gpg-agent inside a runsv process (part of runit package), that
monitors the process, and in case it breaks, it shall restart it.
Unfortunately gpg-agent forks into background, and thus I cannot
monitor if it's running from inside runsv.
Thus I need to make gpg-agent behave just like `gpg-agent
--server` (not forking into background), but using the sockets (just
like --daemon).
Anyway, I've modified the latest source code (2.0.13), file
agent/gpg-agent.c, to add another option --daemon-fg, that shall not
fork in background. (The patch is attached.) (I'm not very proud of
the patch but it does the job. Hope I've not broken anything... :) )
So I would like to ask the maintainer of gpg-agent to look upon
it, and either include it, either (if time allows him) provide such an
option.
Thanks,
Ciprian.
-------------- next part --------------
diff --git a/agent/gpg-agent.c b/agent/gpg-agent.c
index 2e81567..ac2dfdb 100644
--- a/agent/gpg-agent.c
+++ b/agent/gpg-agent.c
@@ -74,6 +74,7 @@ enum cmd_and_opt_values
oLogFile,
oServer,
oDaemon,
+ oDaemonFg,
oBatch,
oPinentryProgram,
@@ -120,6 +121,7 @@ static ARGPARSE_OPTS opts[] = {
{ oServer, "server", 0, N_("run in server mode (foreground)") },
{ oDaemon, "daemon", 0, N_("run in daemon mode (background)") },
+ { oDaemonFg, "daemon-fg", 0, N_("run in daemon mode (foreground)") },
{ oVerbose, "verbose", 0, N_("verbose") },
{ oQuiet, "quiet", 0, N_("be somewhat more quiet") },
{ oSh, "sh", 0, N_("sh-style command output") },
@@ -743,6 +745,7 @@ main (int argc, char **argv )
case oSh: csh_style = 0; break;
case oServer: pipe_server = 1; break;
case oDaemon: is_daemon = 1; break;
+ case oDaemonFg: is_daemon = 2; break;
case oDisplay: default_display = xstrdup (pargs.r.ret_str); break;
case oTTYname: default_ttyname = xstrdup (pargs.r.ret_str); break;
@@ -996,7 +999,10 @@ main (int argc, char **argv )
pid = getpid ();
printf ("set GPG_AGENT_INFO=%s;%lu;1\n", socket_name, (ulong)pid);
#else /*!HAVE_W32_SYSTEM*/
- pid = fork ();
+ if (is_daemon == 1)
+ pid = fork ();
+ else
+ pid = getpid ();
if (pid == (pid_t)-1)
{
log_fatal ("fork failed: %s\n", strerror (errno) );
@@ -1007,7 +1013,8 @@ main (int argc, char **argv )
char *infostr, *infostr_ssh_sock, *infostr_ssh_pid;
/* Close the socket FD. */
- close (fd);
+ if (is_daemon == 1)
+ close (fd);
/* Note that we used a standard fork so that Pth runs in
both the parent and the child. The pth_fork would
@@ -1019,18 +1026,21 @@ main (int argc, char **argv )
right now and thus we restore it. That is not strictly
necessary but some programs falsely assume a cleared
signal mask. */
- if ( !pth_kill () )
- log_error ("pth_kill failed in forked process\n");
+ if (is_daemon == 1)
+ if ( !pth_kill () )
+ log_error ("pth_kill failed in forked process\n");
#ifdef HAVE_SIGPROCMASK
- if (startup_signal_mask_valid)
- {
- if (sigprocmask (SIG_SETMASK, &startup_signal_mask, NULL))
- log_error ("error restoring signal mask: %s\n",
- strerror (errno));
- }
- else
- log_info ("no saved signal mask\n");
+ if (is_daemon == 1) {
+ if (startup_signal_mask_valid)
+ {
+ if (sigprocmask (SIG_SETMASK, &startup_signal_mask, NULL))
+ log_error ("error restoring signal mask: %s\n",
+ strerror (errno));
+ }
+ else
+ log_info ("no saved signal mask\n");
+ }
#endif /*HAVE_SIGPROCMASK*/
/* Create the info string: :: */
@@ -1090,6 +1100,10 @@ main (int argc, char **argv )
if (argc)
{ /* Run the program given on the commandline. */
+ if (is_daemon != 1) {
+ log_error ("no command expected.\n");
+ exit (1);
+ }
if (putenv (infostr))
{
log_error ("failed to set environment: %s\n",
@@ -1128,7 +1142,7 @@ main (int argc, char **argv )
{
/* Print the environment string, so that the caller can use
shell's eval to set it */
- if (csh_style)
+ if (is_daemon == 1 && csh_style)
{
*strchr (infostr, '=') = ' ';
printf ("setenv %s\n", infostr);
@@ -1140,7 +1154,7 @@ main (int argc, char **argv )
printf ("setenv %s\n", infostr_ssh_pid);
}
}
- else
+ else if (is_daemon == 1)
{
printf ( "%s; export GPG_AGENT_INFO;\n", infostr);
if (opt.ssh_support)
@@ -1155,7 +1169,8 @@ main (int argc, char **argv )
xfree (infostr_ssh_sock);
xfree (infostr_ssh_pid);
}
- exit (0);
+ if (is_daemon == 1)
+ exit (0);
}
/*NOTREACHED*/
} /* End parent */
@@ -1185,7 +1200,7 @@ main (int argc, char **argv )
}
}
}
- if (setsid() == -1)
+ if (is_daemon == 1 && setsid() == -1)
{
log_error ("setsid() failed: %s\n", strerror(errno) );
cleanup ();
From David.Gray at turpin-distribution.com Mon Oct 12 17:46:20 2009
From: David.Gray at turpin-distribution.com (David Gray)
Date: Mon, 12 Oct 2009 16:46:20 +0100
Subject: Testing the exit status
In-Reply-To: <87zl7xorub.fsf@vigenere.g10code.de>
References: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local><87ws33qqtq.fsf@vigenere.g10code.de><33CE89420E3A834A82E48C2C747A7061029239AF@HERMES.turpin-bg.local>
<87zl7xorub.fsf@vigenere.g10code.de>
Message-ID: <33CE89420E3A834A82E48C2C747A7061029239BA@HERMES.turpin-bg.local>
Hi Werner,
Thanks for the info. I'm still not clear on how to use the argument
"status-fd 2"
though. Could you possibly give me an example?
I originally opened the file doc/DETAILS with notepad but it was quite
unreadable.
Downloaded Starksoft GnuPG wrapper but it's not compatible with GPG v2.
Contacted the
auther who is looking at an upgrade.
Regards
David
-----Original Message-----
From: Werner Koch [mailto:wk at gnupg.org]
Sent: 12 October 2009 11:00
To: David Gray
Cc: gnupg-users at gnupg.org
Subject: Re: Testing the exit status
On Mon, 12 Oct 2009 11:29, David.Gray at turpin-distribution.com said:
> Can you tell me what the numeric arguments are for status-fd?
That is the file descriptor obn which output should happen. Usualy you
woul use
--status-fd 2
to output to stderr; however how can use arbitrary file descriptors.
> I've downloaded the source for GPG and looked at the doc/DETAILS
> file but on Windows this is unreadable.
Read it in an editor (e.g. notepad). As with all code we use Unix line
endings (LF) and not Windows line endings (CR,LF).
> Also it seems as if gpgme is not available for Windows, is this
correct?
It is available for Windows. Simply install gpg4win (the light version
is sufficient) and you find the gpgme dll in the install directory.
libgpgme-11.dll is the native one, libgpgme-glib-11.dll is the one to
use with GLIB based software and libgpgme-qt-11.dll the one to use with
QT based software. Note that the file gpgme-w32spawn.exe must be in the
same directory as the DLL. The header file is identical for Unix and
Windows, a manual is online at
http://gnupg.org/documentation/manuals.en.html .
> I'm running GPG from a C# application using the Process class. If I
> understand
There is a C# wrapper for GPGME as well, please use a search machine to
locate it.
> correctly then you are suggesting I use status-fd to redirect to a
file
> and then
> open this to interrogate the results.
No, you need to use pipes for that.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
Registered Office: Turpin Distribution Services Ltd, Pegasus Drive, Stratton Business Park, Biggleswade, Bedfordshire, SG18 8TQ, UK. ***** Registered in England No. 1331778 ***** This email may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorised use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.
From wk at gnupg.org Tue Oct 13 10:05:31 2009
From: wk at gnupg.org (Werner Koch)
Date: Tue, 13 Oct 2009 10:05:31 +0200
Subject: How to enable the reader's keypad
In-Reply-To: <1390349622.8969821255023978322.JavaMail.root@zimbra7-e1.priv.proxad.net>
(tux tsndcb's message of "Thu, 8 Oct 2009 19:46:18 +0200 (CEST)")
References: <1390349622.8969821255023978322.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <87aazvwwfo.fsf@vigenere.g10code.de>
On Thu, 8 Oct 2009 19:46, tux.tsndcb at free.fr said:
> On my scdaemon.conf I've not disable-keypad
> So how to do this ?
The keypad is only enabled for certain readers:
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.
Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From wk at gnupg.org Mon Oct 12 19:22:28 2009
From: wk at gnupg.org (Werner Koch)
Date: Mon, 12 Oct 2009 19:22:28 +0200
Subject: Testing the exit status
In-Reply-To: <33CE89420E3A834A82E48C2C747A7061029239BA@HERMES.turpin-bg.local>
(David Gray's message of "Mon, 12 Oct 2009 16:46:20 +0100")
References: <33CE89420E3A834A82E48C2C747A7061029239AE@HERMES.turpin-bg.local>
<87ws33qqtq.fsf@vigenere.g10code.de>
<33CE89420E3A834A82E48C2C747A7061029239AF@HERMES.turpin-bg.local>
<87zl7xorub.fsf@vigenere.g10code.de>
<33CE89420E3A834A82E48C2C747A7061029239BA@HERMES.turpin-bg.local>
Message-ID: <87k4z0wmqz.fsf@vigenere.g10code.de>
On Mon, 12 Oct 2009 17:46, David.Gray at turpin-distribution.com said:
> Thanks for the info. I'm still not clear on how to use the argument
> "status-fd 2"
Writing to a file descriptor is basic technique on almost all systems.
You may want to consult the APUE [1] to see how it works.
> I originally opened the file doc/DETAILS with notepad but it was quite
> unreadable.
I have no problems to read it; see below
Shalom-Salam,
Werner
[1]
http://bookzilla.de/shop/action/productDetails/6878129/w_richard_stevens_stephen_a_rago_advanced_programming_in_the_unix_environment_0321525949.html#produktbeschreibung
doc/DETAILs:
-*- text -*-
Format of colon listings
========================
First an example:
$ gpg --fixed-list-mode --with-colons --list-keys \
--with-fingerprint --with-fingerprint wk at gnupg.org
pub:f:1024:17:6C7EE1B8621CC013:899817715:1055898235::m:::scESC:
fpr:::::::::ECAF7590EB3443B5C7CF3ACB6C7EE1B8621CC013:
uid:f::::::::Werner Koch :
uid:f::::::::Werner Koch :
sub:f:1536:16:06AD222CADF6A6E1:919537416:1036177416:::::e:
fpr:::::::::CF8BCC4B18DE08FCD8A1615906AD222CADF6A6E1:
sub:r:1536:20:5CE086B5B5A18FF4:899817788:1025961788:::::esc:
fpr:::::::::AB059359A3B81F410FCFF97F5CE086B5B5A18FF4:
The double --with-fingerprint prints the fingerprint for the subkeys
too. --fixed-list-mode is the modern listing way printing dates in
seconds since Epoch and does not merge the first userID with the pub
record; gpg2 does this by default and the option is a dummy.
1. Field: Type of record
pub = public key
crt = X.509 certificate
crs = X.509 certificate and private key available
sub = subkey (secondary key)
sec = secret key
ssb = secret subkey (secondary key)
uid = user id (only field 10 is used).
uat = user attribute (same as user id except for field 10).
sig = signature
rev = revocation signature
fpr = fingerprint: (fingerprint is in field 10)
pkd = public key data (special field format, see below)
grp = reserved for gpgsm
rvk = revocation key
tru = trust database information
spk = signature subpacket
2. Field: A letter describing the calculated validity. This is a single
letter, but be prepared that additional information may follow
in some future versions. (not used for secret keys)
o = Unknown (this key is new to the system)
i = The key is invalid (e.g. due to a missing self-signature)
d = The key has been disabled
(deprecated - use the 'D' in field 12 instead)
r = The key has been revoked
e = The key has expired
- = Unknown validity (i.e. no value assigned)
q = Undefined validity
'-' and 'q' may safely be treated as the same
value for most purposes
n = The key is valid
m = The key is marginal valid.
f = The key is fully valid
u = The key is ultimately valid. This often means
that the secret key is available, but any key may
be marked as ultimately valid.
If the validity information is given for a UID or UAT
record, it describes the validity calculated based on this
user ID. If given for a key record it describes the best
validity taken from the best rated user ID.
For X.509 certificates a 'u' is used for a trusted root
certificate (i.e. for the trust anchor) and an 'f' for all
other valid certificates.
3. Field: length of key in bits.
4. Field: Algorithm: 1 = RSA
16 = Elgamal (encrypt only)
17 = DSA (sometimes called DH, sign only)
20 = Elgamal (sign and encrypt - don't use them!)
(for other id's see include/cipher.h)
5. Field: KeyID
6. Field: Creation Date (in UTC). For UID and UAT records, this is
the self-signature date. Note that the date is usally
printed in seconds since epoch, however, we are migrating
to an ISO 8601 format (e.g. "19660205T091500"). This is
currently only relevant for X.509. A simple way to detect
the new format is to scan for the 'T'.
7. Field: Key or user ID/user attribute expiration date or empty if none.
8. Field: Used for serial number in crt records (used to be the Local-ID).
For UID and UAT records, this is a hash of the user ID contents
used to represent that exact user ID. For trust signatures,
this is the trust depth seperated by the trust value by a
space.
9. Field: Ownertrust (primary public keys only)
This is a single letter, but be prepared that additional
information may follow in some future versions. For trust
signatures with a regular expression, this is the regular
expression value, quoted as in field 10.
10. Field: User-ID. The value is quoted like a C string to avoid
control characters (the colon is quoted "\x3a").
For a "pub" record this field is not used on --fixed-list-mode.
A UAT record puts the attribute subpacket count here, a
space, and then the total attribute subpacket size.
In gpgsm the issuer name comes here
An FPR record stores the fingerprint here.
The fingerprint of an revocation key is stored here.
11. Field: Signature class as per RFC-4880. This is a 2 digit
hexnumber followed by either the letter 'x' for an
exportable signature or the letter 'l' for a local-only
signature. The class byte of an revocation key is also
given here, 'x' and 'l' is used the same way. IT is not
used for X.509.
12. Field: Key capabilities:
e = encrypt
s = sign
c = certify
a = authentication
A key may have any combination of them in any order. In
addition to these letters, the primary key has uppercase
versions of the letters to denote the _usable_
capabilities of the entire key, and a potential letter 'D'
to indicate a disabled key.
13. Field: Used in FPR records for S/MIME keys to store the
fingerprint of the issuer certificate. This is useful to
build the certificate path based on certificates stored in
the local keyDB; it is only filled if the issuer
certificate is available. The root has been reached if
this is the same string as the fingerprint. The advantage
of using this value is that it is guaranteed to have been
been build by the same lookup algorithm as gpgsm uses.
For "uid" records this lists the preferences in the same
way the gpg's --edit-key menu does.
For "sig" records, this is the fingerprint of the key that
issued the signature. Note that this is only filled in if
the signature verified correctly. Note also that for
various technical reasons, this fingerprint is only
available if --no-sig-cache is used.
14. Field Flag field used in the --edit menu output:
15. Field Used in sec/sbb to print the serial number of a token
(internal protect mode 1002) or a '#' if that key is a
simple stub (internal protect mode 1001)
All dates are displayed in the format yyyy-mm-dd unless you use the
option --fixed-list-mode in which case they are displayed as seconds
since Epoch. More fields may be added later, so parsers should be
prepared for this. When parsing a number the parser should stop at the
first non-number character so that additional information can later be
added.
If field 1 has the tag "pkd", a listing looks like this:
pkd:0:1024:B665B1435F4C2 .... FF26ABB:
! ! !-- the value
! !------ for information number of bits in the value
!--------- index (eg. DSA goes from 0 to 3: p,q,g,y)
Example for a "tru" trust base record:
tru:o:0:1166697654:1:3:1:5
The fields are:
2: Reason for staleness of trust. If this field is empty, then the
trustdb is not stale. This field may have multiple flags in it:
o: Trustdb is old
t: Trustdb was built with a different trust model than the one we
are using now.
3: Trust model:
0: Classic trust model, as used in PGP 2.x.
1: PGP trust model, as used in PGP 6 and later. This is the same
as the classic trust model, except for the addition of trust
signatures.
GnuPG before version 1.4 used the classic trust model by default.
GnuPG 1.4 and later uses the PGP trust model by default.
4: Date trustdb was created in seconds since 1970-01-01.
5: Date trustdb will expire in seconds since 1970-01-01.
6: Number of marginally trusted users to introduce a new key signer
(gpg's option --marginals-needed)
7: Number of completely trusted users to introduce a new key signer.
(gpg's option --completes-needed)
8: Maximum depth of a certification chain.
*gpg's option --max-cert-depth)
The "spk" signature subpacket records have the fields:
2: Subpacket number as per RFC-4880 and later.
3: Flags in hex. Currently the only two bits assigned are 1, to
indicate that the subpacket came from the hashed part of the
signature, and 2, to indicate the subpacket was marked critical.
4: Length of the subpacket. Note that this is the length of the
subpacket, and not the length of field 5 below. Due to the need
for %-encoding, the length of field 5 may be up to 3x this value.
5: The subpacket data. Printable ASCII is shown as ASCII, but other
values are rendered as %XX where XX is the hex value for the byte.
Format of the "--status-fd" output
==================================
Every line is prefixed with "[GNUPG:] ", followed by a keyword with
the type of the status line and a some arguments depending on the
type (maybe none); an application should always be prepared to see
more arguments in future versions.
NEWSIG
May be issued right before a signature verification starts. This
is useful to define a context for parsing ERROR status
messages. No arguments are currently defined.
GOODSIG
The signature with the keyid is good. For each signature only
one of the three codes GOODSIG, BADSIG or ERRSIG will be
emitted and they may be used as a marker for a new signature.
The username is the primary one encoded in UTF-8 and %XX
escaped. The fingerprint may be used instead of the long keyid
if it is available. This is the case with CMS and might
eventually also be available for OpenPGP.
EXPSIG
The signature with the keyid is good, but the signature is
expired. The username is the primary one encoded in UTF-8 and
%XX escaped. The fingerprint may be used instead of the long
keyid if it is available. This is the case with CMS and might
eventually also be available for OpenPGP.
EXPKEYSIG
The signature with the keyid is good, but the signature was
made by an expired key. The username is the primary one
encoded in UTF-8 and %XX escaped. The fingerprint may be used
instead of the long keyid if it is available. This is the
case with CMS and might eventually also be available for
OpenPGP.
REVKEYSIG
The signature with the keyid is good, but the signature was
made by a revoked key. The username is the primary one encoded
in UTF-8 and %XX escaped. The fingerprint may be used instead
of the long keyid if it is available. This is the case with
CMS and might eventually also be available for OpenPGP.
BADSIG
The signature with the keyid has not been verified okay. The
username is the primary one encoded in UTF-8 and %XX
escaped. The fingerprint may be used instead of the long keyid
if it is available. This is the case with CMS and might
eventually also be available for OpenPGP.
ERRSIG \
It was not possible to check the signature. This may be
caused by a missing public key or an unsupported algorithm. A
RC of 4 indicates unknown algorithm, a 9 indicates a missing
public key. The other fields give more information about this
signature. sig_class is a 2 byte hex-value. The fingerprint
may be used instead of the long keyid if it is available.
This is the case with CMS and might eventually also be
available for OpenPGP.
Note, that TIMESTAMP may either be a number with seconds since
epoch or an ISO 8601 string which can be detected by the
presence of the letter 'T' inside.
VALIDSIG
[ ]
The signature with the keyid is good. This is the same as
GOODSIG but has the fingerprint as the argument. Both status
lines are emitted for a good signature. All arguments here
are on one long line. sig-timestamp is the signature creation
time in seconds after the epoch. expire-timestamp is the
signature expiration time in seconds after the epoch (zero
means "does not expire"). sig-version, pubkey-algo, hash-algo,
and sig-class (a 2-byte hex value) are all straight from the
signature packet. PRIMARY-KEY-FPR is the fingerprint of the
primary key or identical to the first argument. This is
useful to get back to the primary key without running gpg
again for this purpose.
The primary-key-fpr parameter is used for OpenPGP and not
available for CMS signatures. The sig-version as well as the
sig class is not defined for CMS and currently set to 0 and 00.
Note, that *-TIMESTAMP may either be a number with seconds
since epoch or an ISO 8601 string which can be detected by the
presence of the letter 'T' inside.
SIG_ID
This is emitted only for signatures of class 0 or 1 which
have been verified okay. The string is a signature id
and may be used in applications to detect replay attacks
of signed messages. Note that only DLP algorithms give
unique ids - others may yield duplicated ones when they
have been created in the same second.
Note, that SIG-TIMESTAMP may either be a number with seconds
since epoch or an ISO 8601 string which can be detected by the
presence of the letter 'T' inside.
ENC_TO
The message is encrypted to this LONG_KEYID. KEYTYPE is the
numerical value of the public key algorithm or 0 if it is not
known, KEYLENGTH is the length of the key or 0 if it is not
known (which is currently always the case). Gpg prints this
line always; Gpgsm only if it knows the certificate.
NODATA
No data has been found. Codes for what are:
1 - No armored data.
2 - Expected a packet but did not found one.
3 - Invalid packet found, this may indicate a non OpenPGP
message.
4 - signature expected but not found
You may see more than one of these status lines.
UNEXPECTED
Unexpected data has been encountered
0 - not further specified 1
TRUST_UNDEFINED
TRUST_NEVER
TRUST_MARGINAL [0 []]
TRUST_FULLY [0 []]
TRUST_ULTIMATE [0 []]
For good signatures one of these status lines are emitted to
indicate the validity of the key used to create the signature.
The error token values are currently only emitted by gpgsm.
VALIDATION_MODEL describes the algorithm used to check the
validity of the key. The defaults are the standard Web of
Trust model for gpg and the the standard X.509 model for
gpgsm. The defined values are
"pgp" for the standard PGP WoT.
"shell" for the standard X.509 model.
"chain" for the chain model.
Note that we use the term "TRUST_" in the status names for
historic reasons; we now speak of validity.
PKA_TRUST_GOOD
PKA_TRUST_BAD
Depending on the outcome of the PKA check one of the above
status codes is emitted in addition to a TRUST_* status.
Without PKA info available or
SIGEXPIRED
This is deprecated in favor of KEYEXPIRED.
KEYEXPIRED
The key has expired. expire-timestamp is the expiration time
in seconds since Epoch. This status line is not very useful
because it will also be emitted for expired subkeys even if
this subkey is not used. To check whether a key used to sign
a message has expired, the EXPKEYSIG status line is to be
used.
Note, that TIMESTAMP may either be a number with seconds since
epoch or an ISO 8601 string which can be detected by the
presence of the letter 'T' inside.
KEYREVOKED
The used key has been revoked by its owner. No arguments yet.
BADARMOR
The ASCII armor is corrupted. No arguments yet.
RSA_OR_IDEA
The IDEA algorithms has been used in the data. A
program might want to fallback to another program to handle
the data if GnuPG failed. This status message used to be emitted
also for RSA but this has been dropped after the RSA patent expired.
However we can't change the name of the message.
SHM_INFO
SHM_GET
SHM_GET_BOOL
SHM_GET_HIDDEN
GET_BOOL
GET_LINE
GET_HIDDEN
GOT_IT
NEED_PASSPHRASE
Issued whenever a passphrase is needed.
keytype is the numerical value of the public key algorithm
or 0 if this is not applicable, keylength is the length
of the key or 0 if it is not known (this is currently always the case).
NEED_PASSPHRASE_SYM
Issued whenever a passphrase for symmetric encryption is needed.
NEED_PASSPHRASE_PIN []
Issued whenever a PIN is requested to unlock a card.
MISSING_PASSPHRASE
No passphrase was supplied. An application which encounters this
message may want to stop parsing immediately because the next message
will probably be a BAD_PASSPHRASE. However, if the application
is a wrapper around the key edit menu functionality it might not
make sense to stop parsing but simply ignoring the following
BAD_PASSPHRASE.
BAD_PASSPHRASE
The supplied passphrase was wrong or not given. In the latter case
you may have seen a MISSING_PASSPHRASE.
GOOD_PASSPHRASE
The supplied passphrase was good and the secret key material
is therefore usable.
DECRYPTION_FAILED
The symmetric decryption failed - one reason could be a wrong
passphrase for a symmetrical encrypted message.
DECRYPTION_OKAY
The decryption process succeeded. This means, that either the
correct secret key has been used or the correct passphrase
for a conventional encrypted message was given. The program
itself may return an errorcode because it may not be possible to
verify a signature for some reasons.
NO_PUBKEY
NO_SECKEY
The key is not available
IMPORT_CHECK
This status is emitted in interactive mode right before
the "import.okay" prompt.
IMPORTED
The keyid and name of the signature just imported
IMPORT_OK []
The key with the primary key's FINGERPRINT has been imported.
Reason flags:
0 := Not actually changed
1 := Entirely new key.
2 := New user IDs
4 := New signatures
8 := New subkeys
16 := Contains private key.
The flags may be ORed.
IMPORT_PROBLEM []
Issued for each import failure. Reason codes are:
0 := "No specific reason given".
1 := "Invalid Certificate".
2 := "Issuer Certificate missing".
3 := "Certificate Chain too long".
4 := "Error storing certificate".
IMPORT_RES
Final statistics on import process (this is one long line)
FILE_START
Start processing a file . indicates the performed
operation:
1 - verify
2 - encrypt
3 - decrypt
FILE_DONE
Marks the end of a file processing which has been started
by FILE_START.
BEGIN_DECRYPTION
END_DECRYPTION
Mark the start and end of the actual decryption process. These
are also emitted when in --list-only mode.
BEGIN_ENCRYPTION
END_ENCRYPTION
Mark the start and end of the actual encryption process.
BEGIN_SIGNING
Mark the start of the actual signing process. This may be used
as an indication that all requested secret keys are ready for
use.
DELETE_PROBLEM reason_code
Deleting a key failed. Reason codes are:
1 - No such key
2 - Must delete secret key first
3 - Ambigious specification
PROGRESS what char cur total
Used by the primegen and Public key functions to indicate progress.
"char" is the character displayed with no --status-fd enabled, with
the linefeed replaced by an 'X'. "cur" is the current amount
done and "total" is amount to be done; a "total" of 0 indicates that
the total amount is not known. The condition
TOATL && CUR == TOTAL
may be used to detect the end of an operation.
Well known values for WHAT:
"pk_dsa" - DSA key generation
"pk_elg" - Elgamal key generation
"primegen" - Prime generation
"need_entropy" - Waiting for new entropy in the RNG
"file:XXX" - processing file XXX
(note that current gpg versions leave out the
"file:" prefix).
"tick" - generic tick without any special meaning - useful
for letting clients know that the server is
still working.
"starting_agent" - A gpg-agent was started because it is not
running as a daemon.
"learncard" Send by the agent and gpgsm while learing
the data of a smartcard.
"card_busy" A smartcard is still working
SIG_CREATED
A signature has been created using these parameters.
type: 'D' = detached
'C' = cleartext
'S' = standard
(only the first character should be checked)
class: 2 hex digits with the signature class
Note, that TIMESTAMP may either be a number with seconds since
epoch or an ISO 8601 string which can be detected by the
presence of the letter 'T' inside.
KEY_CREATED []
A key has been created
type: 'B' = primary and subkey
'P' = primary
'S' = subkey
The fingerprint is one of the primary key for type B and P and
the one of the subkey for S. Handle is an arbitrary
non-whitespace string used to match key parameters from batch
key creation run.
KEY_NOT_CREATED []
The key from batch run has not been created due to errors.
SESSION_KEY :
The session key used to decrypt the message. This message will
only be emitted when the special option --show-session-key
is used. The format is suitable to be passed to the option
--override-session-key
NOTATION_NAME
NOTATION_DATA
name and string are %XX escaped; the data may be split
among several NOTATION_DATA lines.
USERID_HINT
Give a hint about the user ID for a certain keyID.
POLICY_URL
string is %XX escaped
BEGIN_STREAM
END_STREAM
Issued by pipemode.
INV_RECP
INV_SGNR
Issued for each unusable recipient/sender. The reasons codes
currently in use are:
0 := "No specific reason given".
1 := "Not Found"
2 := "Ambigious specification"
3 := "Wrong key usage"
4 := "Key revoked"
5 := "Key expired"
6 := "No CRL known"
7 := "CRL too old"
8 := "Policy mismatch"
9 := "Not a secret key"
10 := "Key not trusted"
11 := "Missing certificate" (e.g. intermediate or root cert.)
Note that for historical reasons the INV_RECP status is also
used for gpgsm's SIGNER command where it relates to signer's
of course. Newer GnuPG versions are using INV_SGNR;
applications should ignore the INV_RECP during the sender's
command processing once they have seen an INV_SGNR. We use
different code so that we can distinguish them while doing an
encrypt+sign.
NO_RECP
NO_SGNR
Issued when no recipients/senders are usable.
ALREADY_SIGNED
Warning: This is experimental and might be removed at any time.
TRUNCATED
The output was truncated to MAXNO items. This status code is issued
for certain external requests
ERROR []
This is a generic error status message, it might be followed
by error location specific data. and
should not contain spaces. The error code is
a either a string commencing with a letter or such a string
prefixed with a numerical error code and an underscore; e.g.:
"151011327_EOF".
ATTRIBUTE
This is one long line issued for each attribute subpacket when
an attribute packet is seen during key listing. is the
fingerprint of the key. is the length of the
attribute subpacket. is the attribute type
(1==image). / indicates that this is the Nth
indexed subpacket of count total subpackets in this attribute
packet. and are from the
self-signature on the attribute packet. If the attribute
packet does not have a valid self-signature, then the
timestamp is 0. are a bitwise OR of:
0x01 = this attribute packet is a primary uid
0x02 = this attribute packet is revoked
0x04 = this attribute packet is expired
CARDCTRL []
This is used to control smartcard operations.
Defined values for WHAT are:
1 = Request insertion of a card. Serialnumber may be given
to request a specific card. Used by gpg 1.4 w/o scdaemon.
2 = Request removal of a card. Used by gpg 1.4 w/o scdaemon.
3 = Card with serialnumber detected
4 = No card available.
5 = No card reader available
6 = No card support available
PLAINTEXT
This indicates the format of the plaintext that is about to be
written. The format is a 1 byte hex code that shows the
format of the plaintext: 62 ('b') is binary data, 74 ('t') is
text data with no character set specified, and 75 ('u') is
text data encoded in the UTF-8 character set. The timestamp
is in seconds since the epoch. If a filename is available it
gets printed as the third argument, percent-escaped as usual.
PLAINTEXT_LENGTH
This indicates the length of the plaintext that is about to be
written. Note that if the plaintext packet has partial length
encoding it is not possible to know the length ahead of time.
In that case, this status tag does not appear.
SIG_SUBPACKET
This indicates that a signature subpacket was seen. The
format is the same as the "spk" record above.
SC_OP_FAILURE []
An operation on a smartcard definitely failed. Currently
there is no indication of the actual error code, but
application should be prepared to later accept more arguments.
Defined values for CODE are:
0 - unspecified error (identically to a missing CODE)
1 - canceled
2 - bad PIN
SC_OP_SUCCESS
A smart card operaion succeeded. This status is only printed
for certain operation and is mostly useful to check whether a
PIN change really worked.
BACKUP_KEY_CREATED fingerprint fname
A backup key named FNAME has been created for the key with
KEYID.
Format of the "--attribute-fd" output
=====================================
When --attribute-fd is set, during key listings (--list-keys,
--list-secret-keys) GnuPG dumps each attribute packet to the file
descriptor specified. --attribute-fd is intended for use with
--status-fd as part of the required information is carried on the
ATTRIBUTE status tag (see above).
The contents of the attribute data is specified by RFC 4880. For
convenience, here is the Photo ID format, as it is currently the only
attribute defined:
Byte 0-1: The length of the image header. Due to a historical
accident (i.e. oops!) back in the NAI PGP days, this is
a little-endian number. Currently 16 (0x10 0x00).
Byte 2: The image header version. Currently 0x01.
Byte 3: Encoding format. 0x01 == JPEG.
Byte 4-15: Reserved, and currently unused.
All other data after this header is raw image (JPEG) data.
Format of the "--list-config" output
====================================
--list-config outputs information about the GnuPG configuration for
the benefit of frontends or other programs that call GnuPG. There are
several list-config items, all colon delimited like the rest of the
--with-colons output. The first field is always "cfg" to indicate
configuration information. The second field is one of (with
examples):
version: the third field contains the version of GnuPG.
cfg:version:1.3.5
pubkey: the third field contains the public key algorithmdcaiphers
this version of GnuPG supports, separated by semicolons. The
algorithm numbers are as specified in RFC-4880.
cfg:pubkey:1;2;3;16;17
cipher: the third field contains the symmetric ciphers this version of
GnuPG supports, separated by semicolons. The cipher numbers
are as specified in RFC-4880.
cfg:cipher:2;3;4;7;8;9;10
digest: the third field contains the digest (hash) algorithms this
version of GnuPG supports, separated by semicolons. The
digest numbers are as specified in RFC-4880.
cfg:digest:1;2;3;8;9;10
compress: the third field contains the compression algorithms this
version of GnuPG supports, separated by semicolons. The
algorithm numbers are as specified in RFC-4880.
cfg:compress:0;1;2;3
group: the third field contains the name of the group, and the fourth
field contains the values that the group expands to, separated
by semicolons.
For example, a group of:
group mynames = paige 0x12345678 joe patti
would result in:
cfg:group:mynames:patti;joe;0x12345678;paige
Key generation
==============
See the Libcrypt manual.
Unattended key generation
=========================
This feature allows unattended generation of keys controlled by a
parameter file. To use this feature, you use --gen-key together with
--batch and feed the parameters either from stdin or from a file given
on the commandline.
The format of this file is as follows:
o Text only, line length is limited to about 1000 chars.
o You must use UTF-8 encoding to specify non-ascii characters.
o Empty lines are ignored.
o Leading and trailing spaces are ignored.
o A hash sign as the first non white space character indicates a comment line.
o Control statements are indicated by a leading percent sign, the
arguments are separated by white space from the keyword.
o Parameters are specified by a keyword, followed by a colon. Arguments
are separated by white space.
o The first parameter must be "Key-Type", control statements
may be placed anywhere.
o Key generation takes place when either the end of the parameter file
is reached, the next "Key-Type" parameter is encountered or at the
control statement "%commit"
o Control statements:
%echo
Print .
%dry-run
Suppress actual key generation (useful for syntax checking).
%commit
Perform the key generation. An implicit commit is done
at the next "Key-Type" parameter.
%pubring
%secring
Do not write the key to the default or commandline given
keyring but to . This must be given before the first
commit to take place, duplicate specification of the same filename
is ignored, the last filename before a commit is used.
The filename is used until a new filename is used (at commit points)
and all keys are written to that file. If a new filename is given,
this file is created (and overwrites an existing one).
Both control statements must be given.
%ask-passphrase
Enable a mode where the command "passphrase" is ignored and
instead the usual passphrase dialog is used. This does not
make sense for batch key generation; however the unattended
key generation feature is also used by GUIs and this feature
relinquishes the GUI from implementing its own passphrase
entry code. This is a global option.
%no-ask-passphrase
Disable the ask-passphrase mode.
o The order of the parameters does not matter except for "Key-Type"
which must be the first parameter. The parameters are only for the
generated keyblock and parameters from previous key generations are not
used. Some syntactically checks may be performed.
The currently defined parameters are:
Key-Type: |
Starts a new parameter block by giving the type of the
primary key. The algorithm must be capable of signing.
This is a required parameter.
Key-Length:
Length of the key in bits. Default is 1024.
Key-Usage:
Space or comma delimited list of key usage, allowed values are
"encrypt", "sign", and "auth". This is used to generate the
key flags. Please make sure that the algorithm is capable of
this usage. Note that OpenPGP requires that all primary keys
are capable of certification, so no matter what usage is given
here, the "cert" flag will be on. If no Key-Usage is
specified, all the allowed usages for that particular
algorithm are used.
Subkey-Type: |
This generates a secondary key. Currently only one subkey
can be handled.
Subkey-Length:
Length of the subkey in bits. Default is 1024.
Subkey-Usage:
Similar to Key-Usage.
Passphrase:
If you want to specify a passphrase for the secret key,
enter it here. Default is not to use any passphrase.
Name-Real:
Name-Comment:
Name-Email:
The 3 parts of a key. Remember to use UTF-8 here.
If you don't give any of them, no user ID is created.
Expire-Date: |([d|w|m|y])
Set the expiration date for the key (and the subkey). It may
either be entered in ISO date format (2000-08-15) or as number
of days, weeks, month or years. The special notation
"seconds=N" is also allowed to directly give an Epoch
value. Without a letter days are assumed. Note that there is
no check done on the overflow of the type used by OpenPGP for
timestamps. Thus you better make sure that the given value
make sense. Although OpenPGP works with time intervals, GnuPG
uses an absolute value internally and thus the last year we
can represent is 2105.
Creation-Date:
Set the creation date of the key as stored in the key
information and which is also part of the fingerprint
calculation. Either a date like "1986-04-26" or a full
timestamp like "19860426T042640" may be used. The time is
considered to be UTC. If it is not given the current time
is used.
Preferences:
Set the cipher, hash, and compression preference values for
this key. This expects the same type of string as "setpref"
in the --edit menu.
Revoker: : [sensitive]
Add a designated revoker to the generated key. Algo is the
public key algorithm of the designated revoker (i.e. RSA=1,
DSA=17, etc.) Fpr is the fingerprint of the designated
revoker. The optional "sensitive" flag marks the designated
revoker as sensitive information. Only v4 keys may be
designated revokers.
Handle:
This is an optional parameter only used with the status lines
KEY_CREATED and KEY_NOT_CREATED. STRING may be up to 100
characters and should not contain spaces. It is useful for
batch key generation to associate a key parameter block with a
status line.
Keyserver:
This is an optional parameter that specifies the preferred
keyserver URL for the key.
Here is an example:
$ cat >foo <
ssb 1024g/8F70E2C0 2000-03-09
Layout of the TrustDB
=====================
The TrustDB is built from fixed length records, where the first byte
describes the record type. All numeric values are stored in network
byte order. The length of each record is 40 bytes. The first record of
the DB is always of type 1 and this is the only record of this type.
FIXME: The layout changed, document it here.
Record type 0:
--------------
Unused record, can be reused for any purpose.
Record type 1:
--------------
Version information for this TrustDB. This is always the first
record of the DB and the only one with type 1.
1 byte value 1
3 bytes 'gpg' magic value
1 byte Version of the TrustDB (2)
1 byte marginals needed
1 byte completes needed
1 byte max_cert_depth
The three items are used to check whether the cached
validity value from the dir record can be used.
1 u32 locked flags [not used]
1 u32 timestamp of trustdb creation
1 u32 timestamp of last modification which may affect the validity
of keys in the trustdb. This value is checked against the
validity timestamp in the dir records.
1 u32 timestamp of last validation [currently not used]
(Used to keep track of the time, when this TrustDB was checked
against the pubring)
1 u32 record number of keyhashtable [currently not used]
1 u32 first free record
1 u32 record number of shadow directory hash table [currently not used]
It does not make sense to combine this table with the key table
because the keyid is not in every case a part of the fingerprint.
1 u32 record number of the trusthashtbale
Record type 2: (directory record)
--------------
Informations about a public key certificate.
These are static values which are never changed without user interaction.
1 byte value 2
1 byte reserved
1 u32 LID . (This is simply the record number of this record.)
1 u32 List of key-records (the first one is the primary key)
1 u32 List of uid-records
1 u32 cache record
1 byte ownertrust
1 byte dirflag
1 byte maximum validity of all the user ids
1 u32 time of last validity check.
1 u32 Must check when this time has been reached.
(0 = no check required)
Record type 3: (key record)
--------------
Informations about a primary public key.
(This is mainly used to lookup a trust record)
1 byte value 3
1 byte reserved
1 u32 LID
1 u32 next - next key record
7 bytes reserved
1 byte keyflags
1 byte pubkey algorithm
1 byte length of the fingerprint (in bytes)
20 bytes fingerprint of the public key
(This is the value we use to identify a key)
Record type 4: (uid record)
--------------
Informations about a userid
We do not store the userid but the hash value of the userid because that
is sufficient.
1 byte value 4
1 byte reserved
1 u32 LID points to the directory record.
1 u32 next next userid
1 u32 pointer to preference record
1 u32 siglist list of valid signatures
1 byte uidflags
1 byte validity of the key calculated over this user id
20 bytes ripemd160 hash of the username.
Record type 5: (pref record)
--------------
This record type is not anymore used.
1 byte value 5
1 byte reserved
1 u32 LID; points to the directory record (and not to the uid record!).
(or 0 for standard preference record)
1 u32 next
30 byte preference data
Record type 6 (sigrec)
-------------
Used to keep track of key signatures. Self-signatures are not
stored. If a public key is not in the DB, the signature points to
a shadow dir record, which in turn has a list of records which
might be interested in this key (and the signature record here
is one).
1 byte value 6
1 byte reserved
1 u32 LID points back to the dir record
1 u32 next next sigrec of this uid or 0 to indicate the
last sigrec.
6 times
1 u32 Local_id of signatures dir or shadow dir record
1 byte Flag: Bit 0 = checked: Bit 1 is valid (we have a real
directory record for this)
1 = valid is set (but may be revoked)
Record type 8: (shadow directory record)
--------------
This record is used to reserve a LID for a public key. We
need this to create the sig records of other keys, even if we
do not yet have the public key of the signature.
This record (the record number to be more precise) will be reused
as the dir record when we import the real public key.
1 byte value 8
1 byte reserved
1 u32 LID (This is simply the record number of this record.)
2 u32 keyid
1 byte pubkey algorithm
3 byte reserved
1 u32 hintlist A list of records which have references to
this key. This is used for fast access to
signature records which are not yet checked.
Note, that this is only a hint and the actual records
may not anymore hold signature records for that key
but that the code cares about this.
18 byte reserved
Record Type 10 (hash table)
--------------
Due to the fact that we use fingerprints to lookup keys, we can
implement quick access by some simple hash methods, and avoid
the overhead of gdbm. A property of fingerprints is that they can be
used directly as hash values. (They can be considered as strong
random numbers.)
What we use is a dynamic multilevel architecture, which combines
hashtables, record lists, and linked lists.
This record is a hashtable of 256 entries; a special property
is that all these records are stored consecutively to make one
big table. The hash value is simple the 1st, 2nd, ... byte of
the fingerprint (depending on the indirection level).
When used to hash shadow directory records, a different table is used
and indexed by the keyid.
1 byte value 10
1 byte reserved
n u32 recnum; n depends on the record length:
n = (reclen-2)/4 which yields 9 for the current record length
of 40 bytes.
the total number of such record which makes up the table is:
m = (256+n-1) / n
which is 29 for a record length of 40.
To look up a key we use the first byte of the fingerprint to get
the recnum from this hashtable and look up the addressed record:
- If this record is another hashtable, we use 2nd byte
to index this hash table and so on.
- if this record is a hashlist, we walk all entries
until we found one a matching one.
- if this record is a key record, we compare the
fingerprint and to decide whether it is the requested key;
Record type 11 (hash list)
--------------
see hash table for an explanation.
This is also used for other purposes.
1 byte value 11
1 byte reserved
1 u32 next next hash list record
n times n = (reclen-5)/5
1 u32 recnum
For the current record length of 40, n is 7
Record type 254 (free record)
---------------
All these records form a linked list of unused records.
1 byte value 254
1 byte reserved (0)
1 u32 next_free
GNU extensions to the S2K algorithm
===================================
S2K mode 101 is used to identify these extensions.
After the hash algorithm the 3 bytes "GNU" are used to make
clear that these are extensions for GNU, the next bytes gives the
GNU protection mode - 1000. Defined modes are:
1001 - do not store the secret part at all
1002 - a stub to access smartcards (not used in 1.2.x)
Other Notes
===========
* For packet version 3 we calculate the keyids this way:
RSA := low 64 bits of n
ELGAMAL := build a v3 pubkey packet (with CTB 0x99) and calculate
a rmd160 hash value from it. This is used as the
fingerprint and the low 64 bits are the keyid.
* Revocation certificates consist only of the signature packet;
"import" knows how to handle this. The rationale behind it is
to keep them small.
OIDs below the GnuPG arc:
=========================
1.3.6.1.4.1.11591.2 GnuPG
1.3.6.1.4.1.11591.2.1 notation
1.3.6.1.4.1.11591.2.1.1 pkaAddress
1.3.6.1.4.1.11591.2.12242973 invalid encoded OID
Keyserver Message Format
=========================
The keyserver may be contacted by a Unix Domain socket or via TCP.
The format of a request is:
====
command-tag
"Content-length:" digits
CRLF
=======
Where command-tag is
NOOP
GET
PUT
DELETE
The format of a response is:
======
"GNUPG/1.0" status-code status-text
"Content-length:" digits
CRLF
============
followed by bytes of data
Status codes are:
o 1xx: Informational - Request received, continuing process
o 2xx: Success - The action was successfully received, understood,
and accepted
o 4xx: Client Error - The request contains bad syntax or cannot be
fulfilled
o 5xx: Server Error - The server failed to fulfill an apparently
valid request
Documentation on HKP (the http keyserver protocol):
A minimalistic HTTP server on port 11371 recognizes a GET for /pks/lookup.
The standard http URL encoded query parameters are this (always key=value):
- op=index (like pgp -kv), op=vindex (like pgp -kvv) and op=get (like
pgp -kxa)
- search=. This is a list of words that must occur in the key.
The words are delimited with space, points, @ and so on. The delimiters
are not searched for and the order of the words doesn't matter (but see
next option).
- exact=on. This switch tells the hkp server to only report exact matching
keys back. In this case the order and the "delimiters" are important.
- fingerprint=on. Also reports the fingerprints when used with 'index' or
'vindex'
The keyserver also recognizes http-POSTs to /pks/add. Use this to upload
keys.
A better way to do this would be a request like:
/pks/lookup/?op=
This can be implemented using Hurd's translator mechanism.
However, I think the whole key server stuff has to be re-thought;
I have some ideas and probably create a white paper.
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From tux.tsndcb at free.fr Tue Oct 13 11:14:32 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Tue, 13 Oct 2009 11:14:32 +0200 (CEST)
Subject: How to enable the reader's keypad
In-Reply-To: <174387797.9653941255425190454.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1125716695.9654061255425272208.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi Werner,
I have add this yesterday in the ccid-driver.c file :
/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};
and
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
But it doesn't works, I've give more information in the [issue1148]
perhaps it because my conf file are wrong :
gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net
gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800
scdaemon.conf :
verbose
and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent
Thank in advanced for your confirmation.
Best Regards
----- Mail Original -----
De: "Werner Koch"
?: "tux tsndcb"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad
On Thu, 8 Oct 2009 19:46, tux.tsndcb at free.fr said:
> On my scdaemon.conf I've not disable-keypad
> So how to do this ?
The keypad is only enabled for certain readers:
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.
Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
From tux.tsndcb at free.fr Tue Oct 13 19:10:32 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Tue, 13 Oct 2009 19:10:32 +0200 (CEST)
Subject: How to enable the reader's keypad
In-Reply-To: <1125716695.9654061255425272208.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1688114904.9749291255453832155.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi Werner,
the Vendor tell to me than I need also this for the reader, but I dont know where to put it :
bNumberMessage = 0x01
bEntryValidationCondition = 0x02
bNumberMessages = 0x03
Thanks in advanced for your return
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 11h14:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad
Hi Werner,
I have add this yesterday in the ccid-driver.c file :
/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};
and
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
But it doesn't works, I've give more information in the [issue1148]
perhaps it because my conf file are wrong :
gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net
gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800
scdaemon.conf :
verbose
and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent
Thank in advanced for your confirmation.
Best Regards
----- Mail Original -----
De: "Werner Koch"
?: "tux tsndcb"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad
On Thu, 8 Oct 2009 19:46, tux.tsndcb at free.fr said:
> On my scdaemon.conf I've not disable-keypad
> So how to do this ?
The keypad is only enabled for certain readers:
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.
Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
From CONNIE.RODRIGUEZ at childrens.com Wed Oct 14 19:55:37 2009
From: CONNIE.RODRIGUEZ at childrens.com (CONNIE RODRIGUEZ)
Date: Wed, 14 Oct 2009 12:55:37 -0500
Subject: GNUPG HELP please
Message-ID: <4AD5CA49.632C.0028.0@childrens.com>
Hello All,
I am a rookie at encrypting and run into a brick wall when I tried to run gnupg on a different server......
I hope someone can help. I was able to successfully run the gnupg on a development system but when I set up gnupg on my test system I received the following warnings and errors. Can you help me?
+ /usr/local/bin/gpg -e -r REWARD /law/test/law/test/interface/watsonwyatt/data/epay.txt
gpg: WARNING: unsafe permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: 4D5AFE2E: There is no assurance this key belongs to the named user
gpg: cannot open `/dev/tty': There is a request to a device or address that does not exist.
Thank you in advance for any help you can provide
Connie Rodriguez
connie.rodriguez at childrens.com
Please consider the environment before printing this e-mail.
This e-mail, facsimile, or letter and any files or attachments transmitted with it contains
information that is confidential and privileged. This information is intended only for the
use of the individual(s) and entity(ies) to whom it is addressed. If you are the intended
recipient, further disclosures are prohibited without proper authorization. If you are not
the intended recipient, any disclosure, copying, printing, or use of this information is
strictly prohibited and possibly a violation of federal or state law and regulations. If you
have received this information in error, please notify Children's Medical Center Dallas
immediately at 214-456-4444 or via e-mail at privacy at childrens.com. Children's Medical
Center Dallas and its affiliates hereby claim all applicable privileges related to this
information.
From tux.tsndcb at free.fr Wed Oct 14 21:41:34 2009
From: tux.tsndcb at free.fr (tux.tsndcb at free.fr)
Date: Wed, 14 Oct 2009 21:41:34 +0200 (CEST)
Subject: How to enable the reader's keypad
In-Reply-To: <1688114904.9749291255453832155.JavaMail.root@zimbra7-e1.priv.proxad.net>
Message-ID: <1797053181.9986591255549294143.JavaMail.root@zimbra7-e1.priv.proxad.net>
Hi Werner,
Do I need to change also something in this two files :
agent/divert-scd.c
scd/app-dinsig.c
Is there a commande line to test reader's keypad acces ?
thanks in advanced for your return.
Best Regard
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 19h10:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad
Hi Werner,
the Vendor tell to me than I need also this for the reader, but I dont know where to put it :
bNumberMessage = 0x01
bEntryValidationCondition = 0x02
bNumberMessages = 0x03
Thanks in advanced for your return
Best Regards
----- Mail Original -----
De: "tux tsndcb"
?: "Werner Koch"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 11h14:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad
Hi Werner,
I have add this yesterday in the ccid-driver.c file :
/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};
and
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
But it doesn't works, I've give more information in the [issue1148]
perhaps it because my conf file are wrong :
gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net
gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800
scdaemon.conf :
verbose
and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent
Thank in advanced for your confirmation.
Best Regards
----- Mail Original -----
De: "Werner Koch"
?: "tux tsndcb"
Cc: gnupg-users at gnupg.org
Envoy?: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad
On Thu, 8 Oct 2009 19:46, tux.tsndcb at free.fr said:
> On my scdaemon.conf I've not disable-keypad
> So how to do this ?
The keypad is only enabled for certain readers:
/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}
You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.
Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
From dkg at fifthhorseman.net Wed Oct 14 22:17:31 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 14 Oct 2009 16:17:31 -0400
Subject: GNUPG HELP please
In-Reply-To: <4AD5CA49.632C.0028.0@childrens.com>
References: <4AD5CA49.632C.0028.0@childrens.com>
Message-ID: <4AD631DB.7040103@fifthhorseman.net>
Hi Connie--
On 10/14/2009 01:55 PM, CONNIE RODRIGUEZ wrote:
> + /usr/local/bin/gpg -e -r REWARD /law/test/law/test/interface/watsonwyatt/data/epay.txt
> gpg: WARNING: unsafe permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
This suggests that your configuration file may be readable or writable
by other users. You can view the permissions on that file with:
ls -l /home/lawbr/.gnupg/gpg.conf
You can lock it down with:
chmod go-rwx /home/lawbr/.gnupg/gpg.conf
(note here that "go-rwx" means "remove (-) read (r), write (w), and
execute (x) from group (g) and all other users (o)" )
If you're not sure about the concept of filesystem permissions, it's
worthwhile to think about them a bit. they'll come up fairly often on
unix systems. wikipedia has a good start:
http://en.wikipedia.org/wiki/File_system_permissions#Notation_of_traditional_Unix_permissions
> gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
This is due to a directory being potentially readable or writable by
other users. You can lock down the "enclosing directory" with:
chmod go-rwx`/home/lawhr/.gnupg/
> gpg: WARNING: using insecure memory!
Search for "insecure memory" in the gpg manual page (try "man gpg") for
more information about this error under the BUGS section. You may
either want to make gpg setuid root (if secure memory is important to
you) or to tell gpg to ignore this particular error by adding the
relvant option to your gpg.conf file.
> gpg: please see http://www.gnupg.org/faq.html for more information
have you read this? It's worth reading! You might be interested in
section 6.1 in particular:
http://www.gnupg.org/faq.html#q6.1
> gpg: 4D5AFE2E: There is no assurance this key belongs to the named user
this is likely because you've imported the "REWARD" key into your remote
system without indicating any particular "ultimate" ownertrust.
gpg does a fair amount of work to make sure that keys belong to who you
think they should belong to -- it doesn't make any sense to encrypt data
to a key if you aren't sure whose key it is.
Presumably, there is someone who is making reasonable assertions about
which keys belong to which entities, and signing those keys. You
probably want to designate "ultimate" ownertrust for that certifier on
your server. For example, if you hold key DECAFBAD privately
(off-server), but you use that key to sign the REWARD key, you could
import the DECAFBAD public key on the server, and then (still on the
server) do:
gpg --edit-key DECAFBAD
trust
and then choose "ultimate" ownertrust. Make sense?
> gpg: cannot open `/dev/tty': There is a request to a device or address that does not exist.
i dunno why this is coming up; what operating system are you running
this on? what version of gpg? did you build it yourself, or is it the
version provided by your OS?
hth,
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 891 bytes
Desc: OpenPGP digital signature
URL:
From CONNIE.RODRIGUEZ at childrens.com Wed Oct 14 23:07:13 2009
From: CONNIE.RODRIGUEZ at childrens.com (CONNIE RODRIGUEZ)
Date: Wed, 14 Oct 2009 16:07:13 -0500
Subject: GNUPG HELP please
In-Reply-To: <4AD631DB.7040103@fifthhorseman.net>
References: <4AD5CA49.632C.0028.0@childrens.com>
<4AD631DB.7040103@fifthhorseman.net>
Message-ID: <4AD5F731.632C.0028.0@childrens.com>
Thank you very much for the very informative information. I have locked down some of the permissions.
I attempted key signing but was not successful. I received the following output:
[lawhr at lsftest1/usr/local/bin # ./gpg --edit-key REWARD
pub 1024D/C2126D6D created: 2009-02-23 expires: never usage: SC
trust: unknown validity: unknown
sub 2048g/4D5AFE2E created: 2009-02-23 expires: never usage: E
[ unknown] (1). REWARD data interchange 2009
Command> sign
gpg: no default secret key: secret key not available
Command>
Any help is appreciated!
Thank you,
Connie Rodriguez
>>> Daniel Kahn Gillmor 10/14/2009 3:17 PM >>>
Hi Connie--
On 10/14/2009 01:55 PM, CONNIE RODRIGUEZ wrote:
> + /usr/local/bin/gpg -e -r REWARD /law/test/law/test/interface/watsonwyatt/data/epay.txt
> gpg: WARNING: unsafe permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
This suggests that your configuration file may be readable or writable
by other users. You can view the permissions on that file with:
ls -l /home/lawbr/.gnupg/gpg.conf
You can lock it down with:
chmod go-rwx /home/lawbr/.gnupg/gpg.conf
(note here that "go-rwx" means "remove (-) read (r), write (w), and
execute (x) from group (g) and all other users (o)" )
If you're not sure about the concept of filesystem permissions, it's
worthwhile to think about them a bit. they'll come up fairly often on
unix systems. wikipedia has a good start:
http://en.wikipedia.org/wiki/File_system_permissions#Notation_of_traditional_Unix_permissions
> gpg: WARNING: unsafe enclosing directory permissions on configuration file `/home/lawhr/.gnupg/gpg.conf'
This is due to a directory being potentially readable or writable by
other users. You can lock down the "enclosing directory" with:
chmod go-rwx`/home/lawhr/.gnupg/
> gpg: WARNING: using insecure memory!
Search for "insecure memory" in the gpg manual page (try "man gpg") for
more information about this error under the BUGS section. You may
either want to make gpg setuid root (if secure memory is important to
you) or to tell gpg to ignore this particular error by adding the
relvant option to your gpg.conf file.
> gpg: please see http://www.gnupg.org/faq.html for more information
have you read this? It's worth reading! You might be interested in
section 6.1 in particular:
http://www.gnupg.org/faq.html#q6.1
> gpg: 4D5AFE2E: There is no assurance this key belongs to the named user
this is likely because you've imported the "REWARD" key into your remote
system without indicating any particular "ultimate" ownertrust.
gpg does a fair amount of work to make sure that keys belong to who you
think they should belong to -- it doesn't make any sense to encrypt data
to a key if you aren't sure whose key it is.
Presumably, there is someone who is making reasonable assertions about
which keys belong to which entities, and signing those keys. You
probably want to designate "ultimate" ownertrust for that certifier on
your server. For example, if you hold key DECAFBAD privately
(off-server), but you use that key to sign the REWARD key, you could
import the DECAFBAD public key on the server, and then (still on the
server) do:
gpg --edit-key DECAFBAD
trust
and then choose "ultimate" ownertrust. Make sense?
> gpg: cannot open `/dev/tty': There is a request to a device or address that does not exist.
i dunno why this is coming up; what operating system are you running
this on? what version of gpg? did you build it yourself, or is it the
version provided by your OS?
hth,
--dkg
Please consider the environment before printing this e-mail.
This e-mail, facsimile, or letter and any files or attachments transmitted with it contains
information that is confidential and privileged. This information is intended only for the
use of the individual(s) and entity(ies) to whom it is addressed. If you are the intended
recipient, further disclosures are prohibited without proper authorization. If you are not
the intended recipient, any disclosure, copying, printing, or use of this information is
strictly prohibited and possibly a violation of federal or state law and regulations. If you
have received this information in error, please notify Children's Medical Center Dallas
immediately at 214-456-4444 or via e-mail at privacy at childrens.com. Children's Medical
Center Dallas and its affiliates hereby claim all applicable privileges related to this
information.
From dkg at fifthhorseman.net Wed Oct 14 23:40:41 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 14 Oct 2009 17:40:41 -0400
Subject: GNUPG HELP please
In-Reply-To: <4AD5F731.632C.0028.0@childrens.com>
References: <4AD5CA49.632C.0028.0@childrens.com> <4AD631DB.7040103@fifthhorseman.net>
<4AD5F731.632C.0028.0@childrens.com>
Message-ID: <4AD64559.1030001@fifthhorseman.net>
Hi Connie--
I'm glad that was useful.
On 10/14/2009 05:07 PM, CONNIE RODRIGUEZ wrote:
> I attempted key signing but was not successful. I received the following output:
>
> [lawhr at lsftest1/usr/local/bin # ./gpg --edit-key REWARD
> pub 1024D/C2126D6D created: 2009-02-23 expires: never usage: SC
> trust: unknown validity: unknown
> sub 2048g/4D5AFE2E created: 2009-02-23 expires: never usage: E
> [ unknown] (1). REWARD data interchange 2009
>
> Command> sign
> gpg: no default secret key: secret key not available
>
> Command>
>
> Any help is appreciated!
It sounds to me like you might be confusing validity with ownertrust.
In my earlier note, i suggested that you *trust* the keyholder of some
key that will certify the keys you are encrypting to.
Instead, it looks to me like you've chosen to try to *sign* one of the
keys you're encrypting to directly from the server.
It helps me to separate out these concepts into two ideas:
0) who do you know (i.e. who can you identify)?
1) who do you trust to identify others?
And since you're dealing with two different gpg installations (one on
the server and one that you control elsewhere) you probably want to
think about those from separate perspectives.
I don't know what you're planning to do on your server, but i'll pretend
for the moment that you're working with a web application which is
expected to recieve information over the web, and then encrypt it to
someone. I'll refer to that someone as the "encryption target".
from the webapp's view, how does it know it's encrypting info to the
right person?
let's say you're the administrator of such a system, and you want the
webapp to believe you when you certify that a certain key belongs to a
given person. Then you (as the admin) would have your own OpenPGP key,
stored off of the server (probably on your own workstation someplace).
Let's assume that key is key ID 0xDECAFBAD. You'd upload the public part
of 0xDECAFBAD to the server, and import it into the webapp's keyring.
After import *as the webapp user* you'd say "i trust the sysadmin to
identify encryption targets" by doing:
gpg --edit-key 0xDECAFBAD
trust
and then designate "ultimate" ownertrust.
Then, you'd use your own key to certify the key belonging to the
encryption target -- you'd "sign the target's public key" with your own
key. Then you'd upload the target's public key (with your
certification) to the server, and import it into the webapp's keyring.
Does this make sense? The advantage of this arrangement is that now
your webapp can be used to encrypt to a variety of people -- you'll just
need to sign their keys, and they can be encryption targets as well.
hope this helps,
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 891 bytes
Desc: OpenPGP digital signature
URL:
From Joachim.Blomberg at vr-leasing.de Thu Oct 15 04:00:37 2009
From: Joachim.Blomberg at vr-leasing.de (Joachim.Blomberg at vr-leasing.de)
Date: Thu, 15 Oct 2009 04:00:37 +0200
Subject: =?ISO-8859-1?Q?Joachim_Blomberg=2FVRD=2FVR-GRUPPE_ist_au=DFer_Haus=2E?=
Message-ID:
Ich werde ab 12.10.2009 nicht im B?ro sein. Ich kehre zur?ck am
17.10.2009.
Ich werde Ihre Nachricht nach meiner R?ckkehr beantworten.
In dringenden F?llen bin auf meinm Dienst-Handy erreichbar .
From CONNIE.RODRIGUEZ at childrens.com Thu Oct 15 16:20:04 2009
From: CONNIE.RODRIGUEZ at childrens.com (CONNIE RODRIGUEZ)
Date: Thu, 15 Oct 2009 09:20:04 -0500
Subject: GNUPG HELP please
In-Reply-To: <4AD64559.1030001@fifthhorseman.net>
References: <4AD5CA49.632C.0028.0@childrens.com> <4AD631DB.7040103@fifthhorseman.net>
<4AD5F731.632C.0028.0@childrens.com><4AD5F731.632C.0028.0@childrens.com>
<4AD64559.1030001@fifthhorseman.net>
Message-ID: <4AD6E944.632C.0028.0@childrens.com>
Great!! Signed and edit key ...Works like a charm. Thank you
>>> Daniel Kahn Gillmor 10/14/2009 4:40 PM >>>
Hi Connie--
I'm glad that was useful.
On 10/14/2009 05:07 PM, CONNIE RODRIGUEZ wrote:
> I attempted key signing but was not successful. I received the following output:
>
> [lawhr at lsftest1/usr/local/bin # ./gpg --edit-key REWARD
> pub 1024D/C2126D6D created: 2009-02-23 expires: never usage: SC
> trust: unknown validity: unknown
> sub 2048g/4D5AFE2E created: 2009-02-23 expires: never usage: E
> [ unknown] (1). REWARD data interchange 2009
>
> Command> sign
> gpg: no default secret key: secret key not available
>
> Command>
>
> Any help is appreciated!
It sounds to me like you might be confusing validity with ownertrust.
In my earlier note, i suggested that you *trust* the keyholder of some
key that will certify the keys you are encrypting to.
Instead, it looks to me like you've chosen to try to *sign* one of the
keys you're encrypting to directly from the server.
It helps me to separate out these concepts into two ideas:
0) who do you know (i.e. who can you identify)?
1) who do you trust to identify others?
And since you're dealing with two different gpg installations (one on
the server and one that you control elsewhere) you probably want to
think about those from separate perspectives.
I don't know what you're planning to do on your server, but i'll pretend
for the moment that you're working with a web application which is
expected to recieve information over the web, and then encrypt it to
someone. I'll refer to that someone as the "encryption target".
from the webapp's view, how does it know it's encrypting info to the
right person?
let's say you're the administrator of such a system, and you want the
webapp to believe you when you certify that a certain key belongs to a
given person. Then you (as the admin) would have your own OpenPGP key,
stored off of the server (probably on your own workstation someplace).
Let's assume that key is key ID 0xDECAFBAD. You'd upload the public part
of 0xDECAFBAD to the server, and import it into the webapp's keyring.
After import *as the webapp user* you'd say "i trust the sysadmin to
identify encryption targets" by doing:
gpg --edit-key 0xDECAFBAD
trust
and then designate "ultimate" ownertrust.
Then, you'd use your own key to certify the key belonging to the
encryption target -- you'd "sign the target's public key" with your own
key. Then you'd upload the target's public key (with your
certification) to the server, and import it into the webapp's keyring.
Does this make sense? The advantage of this arrangement is that now
your webapp can be used to encrypt to a variety of people -- you'll just
need to sign their keys, and they can be encryption targets as well.
hope this helps,
--dkg
Please consider the environment before printing this e-mail.
This e-mail, facsimile, or letter and any files or attachments transmitted with it contains
information that is confidential and privileged. This information is intended only for the
use of the individual(s) and entity(ies) to whom it is addressed. If you are the intended
recipient, further disclosures are prohibited without proper authorization. If you are not
the intended recipient, any disclosure, copying, printing, or use of this information is
strictly prohibited and possibly a violation of federal or state law and regulations. If you
have received this information in error, please notify Children's Medical Center Dallas
immediately at 214-456-4444 or via e-mail at privacy at childrens.com. Children's Medical
Center Dallas and its affiliates hereby claim all applicable privileges related to this
information.
From danm at prime.gushi.org Fri Oct 16 03:37:08 2009
From: danm at prime.gushi.org (Dan Mahoney, System Admin)
Date: Thu, 15 Oct 2009 21:37:08 -0400 (EDT)
Subject: A lot of questions about CERT, PKA and make-dns-cert
Message-ID:
All,
I'm in the process of writing a blog entry about the PKA and CERT methods.
A couple people have written them a long time ago, and I'd like to bring
some of the info up to date. (If this is better asked on gnupg-dev, let me know).
For starters:
1) Currently the only tool that can generate a CERT record, make-dns-cert,
is not built or packaged by default under any os I've found (I've tried
FreeBSD and ubuntu). It has no documentation, no examples, and only a
terse 4-line usage summary. I've also seen a few bugs reported with it,
that I don't know if they're fixed, such as not handling whitespace in the
key fingerprint properly.
2) I realize this is a fringe feature, but other than a few scattered blog
posts that reference each other, some of which are written by gnupg
developers, info on these methods is HARD TO FIND. There's nothing in the
docs/faq about this, at all. I think adoption would be much more
widespread if this were a faq-able item. It's mentioned once in the
manpage, once in the default gnupg.conf, and that's really it. If you
document it, people will use it (and with thawte dropping personal
freemail certs lately, this is something you want).
3) As far as I know, PKA isn't standardized in any RFC. Has this been
changed? I saw mention of applying to IANA for its own typecode. Is
there a list somewhere of what uri types are supported? I saw talk of it
not supporting http 1.1, but that may be fixed with curl.
Of the two methods, I tend to actually prefer PKA because it lets me
delegate _pka.example.com to its own sub-zone, whereas CERT records must
be inserted into the main zone.
4) Try though I might, I can't seem to get my full-key in CERT format to
recognize. I am not sure if this is because my key is "complicated" (i.e.
it has subkeys), because the cert is not under my primary uid, or because
I just plain exported it wrong.
I'm running:
echo foo | gpg -v -v --auto-key-locate cert --recipient gushi at gushi.org
--encrypt -a
And get gpg: error retrieving `gushi at gushi.org' via DNS CERT: No fingerprint
I exported my key with:
gpg --export --export-options minimal > file; and make-dns-cert -n
gushi.gushi.org -f file
It's still live if anyone wants to try.
5) Finally, the quality of records being generated, while consistent with
rfc3597, leaves them as a real bear to manage, and import. If you're
going to export them in hex, could we please also get whitespace so we can
get this into an editor easily? Ideally, the things would just be base64
encoded, in accordance with rfc4398.
Most versions of bind9 understand the CERT record, with base64
representation, and numeric typecodes. bind9.6 understands the PGP type
value mnemonic but not IPGP. BIND 9.7 understands IPGP.
What would be really, really cool, is step by step instructions for
exporting, or hell, let gpg generate these records, the way ssh-keygen
generates SSHFP records.
Those are my thoughts.
-Dan
--
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
From dshaw at jabberwocky.com Fri Oct 16 05:27:52 2009
From: dshaw at jabberwocky.com (David Shaw)
Date: Thu, 15 Oct 2009 23:27:52 -0400
Subject: A lot of questions about CERT, PKA and make-dns-cert
In-Reply-To:
References:
Message-ID:
On Oct 15, 2009, at 9:37 PM, Dan Mahoney, System Admin wrote:
> 1) Currently the only tool that can generate a CERT record, make-dns-
> cert, is not built or packaged by default under any os I've found
> (I've tried FreeBSD and ubuntu). It has no documentation, no
> examples, and only a terse 4-line usage summary. I've also seen a
> few bugs reported with it, that I don't know if they're fixed, such
> as not handling whitespace in the key fingerprint properly.
The whitespace issue was handled back in 2006 (one day after the
program was added to GnuPG, as it happens). Possibly you saw an email
from someone who was tracking the code repository in between
releases. There is no version of GnuPG that was ever released with
the bug.
> 2) I realize this is a fringe feature, but other than a few
> scattered blog posts that reference each other, some of which are
> written by gnupg developers, info on these methods is HARD TO FIND.
> There's nothing in the docs/faq about this, at all. I think
> adoption would be much more widespread if this were a faq-able
> item. It's mentioned once in the manpage, once in the default
> gnupg.conf, and that's really it. If you document it, people will
> use it (and with thawte dropping personal freemail certs lately,
> this is something you want).
Even if the documentation was better (and I agree, it is poorly
documented), I don't think CERT or PKA would be a very widely used
feature. The reality is that the majority of users do not have the
kind of access to DNS that CERT requires. PKA is a bit better in this
regard as it uses TXT records, which can at least be used by people
who have some web-based DNS configuration for their domain. I don't
know of many of those configuration tools that do CERT at all (we're
talking text-files-and-bind usually for CERT). Whether TXT or CERT,
though, it's a fairly high barrier for many users.
I do encourage you to document it better, and I'm willing to help
explain wherever necessary, or make code changes if there is something
that could be done better.
> 3) As far as I know, PKA isn't standardized in any RFC. Has this
> been changed? I saw mention of applying to IANA for its own
> typecode. Is there a list somewhere of what uri types are
> supported? I saw talk of it not supporting http 1.1, but that may
> be fixed with curl.
If you build GnuPG with curl (which is the default, assuming you have
curl), then you have HTTP 1.1 support. That said, is there a
particular HTTP 1.1 feature that you need here? After the PKA parsing
happens, GPG is just doing a regular HTTP GET.
> 4) Try though I might, I can't seem to get my full-key in CERT
> format to recognize. I am not sure if this is because my key is
> "complicated" (i.e. it has subkeys), because the cert is not under
> my primary uid, or because I just plain exported it wrong.
>
> I'm running:
>
> echo foo | gpg -v -v --auto-key-locate cert --recipient gushi at gushi.org
> --encrypt -a
>
> And get gpg: error retrieving `gushi at gushi.org' via DNS CERT: No
> fingerprint
>
> I exported my key with:
>
> gpg --export --export-options minimal > file; and make-dns-cert -n
> gushi.gushi.org -f file
It works fine for me. What version of GPG are you using?
Incidentally, you have two different CERT records for gushi.gushi.org
at the same time. You have both a fingerprint-style answer and a full-
key answer. This is not a major problem (GPG won't care - it'll just
take the first one that parses), but if your nameserver does some sort
of round-robining, it can be confusing as to which record is the one
that gets used.
> 5) Finally, the quality of records being generated, while consistent
> with rfc3597, leaves them as a real bear to manage, and import. If
> you're going to export them in hex, could we please also get
> whitespace so we can get this into an editor easily? Ideally, the
> things would just be base64 encoded, in accordance with rfc4398.
>
> Most versions of bind9 understand the CERT record, with base64
> representation, and numeric typecodes. bind9.6 understands the PGP
> type value mnemonic but not IPGP. BIND 9.7 understands IPGP.
When I wrote the code, precious few nameservers understood any of this
(and none understood IPGP at all - that patch only went into BIND a
few months ago). That's why the record is TYPE37 and not CERT. It's
ugly, but it was the least common denominator. It has been a few
years since then. Possibly it's time to upgrade.
David
From danm at prime.gushi.org Fri Oct 16 06:34:46 2009
From: danm at prime.gushi.org (Dan Mahoney, System Admin)
Date: Fri, 16 Oct 2009 00:34:46 -0400 (EDT)
Subject: A lot of questions about CERT, PKA and make-dns-cert
In-Reply-To:
References: