Reusing signed user ID or attribute

[Hauke Laging]

Am So 19.01.2014, 15:55:51 schrieb Daniele Ricci:
> Ok, so I have to conclude it's implementation specific?
> I'm using a custom user attribute to store something that can change
> quite often (privacy lists for a chat user). What do you suggest?

My first thought is: Why should it make sense to put this data into a 
certificate?

Use a simple file with a simple signature. Let the signature expire 
every few days (or hours, whatever you need).

You may put the URL of the file into the certificate using a notation.


Hauke
-- 
Crypto für alle: http://www.openpgp-schulungen.de/fuer/unterstuetzer/
http://userbase.kde.org/Concepts/OpenPGP_Help_Spread
OpenPGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 572 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20140119/2d77ee76/attachment.sig>