On Fri, 2005-08-12 at 10:51 -0700, [EMAIL PROTECTED] wrote:
> David Srbecky dsrbecky at gmail.com
> Thu Aug 11 18:19:54 CEST 2005 wrote:
>
> ] I have payed with the idea of using experimental subpackets
> ] of 'User Attribute Packet' and here is what I came up with:
> doesn't this pose some risk
> It there any way I can use GnuPG to store and load this information?
It seems to me that if I call "gpg.exe --status-fd 1 --attribute-fd 1
--list-keys " I can read the experimental subpackets.
Is there any way I can write them?
David
signature.asc
Description: OpenPGP digital signature
David Srbecky dsrbecky at gmail.com
Thu Aug 11 18:19:54 CEST 2005 wrote:
] I have payed with the idea of using experimental subpackets
] of 'User Attribute Packet' and here is what I came up with:
] Named Attribute Subpacket (type 100)
] Datatypes:
0 - reserved
1 - no data (it is just
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David Srbecky wrote:
> vCard Subpacket (type 102)
> --
> Subpacket specific data:
>magic identification number
>data - content of the vCard file
>
*cough*
- --
Alphax | /"\
Encrypte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 12 Aug 2005, David Srbecky wrote:
> Unfortunately I am not asking for problem, the problem is already here.
> Users already can upload their photo albums to keyserver and no-one can
> stop them. One vCard and a few preferences really won't make
Joe Smith wrote:
Be careful with this. First of all both the second and third packet can
be implemented as the first packet type.
That's the point of the first packet - to be able to express anything
the user can think of. However, the other two packets are there to save
space by not using stri
Be careful with this. First of all both the second and third packet can be
implemented as the first packet type. Second encouraging users to place
extra data into theie keys is just asking for problem. Imaginge when
somebody decides to attaches a 50 MiB mpeg to their key, and uploads it to
the
Hello,
I have payed with the idea of using experimental subpackets of 'User
Attribute Packet' and here is what I came up with:
Named Attribute Subpacket (type 100)
--
Subpacket specific data:
magic identification number
datatype - identifier - eg. 4 - UTF8
