On Aug 9, 2013, at 2:43 AM, Khelben Blackstaff
wrote:
> I only replied to Mr. Shaw and not to the list so i send this again.
>
> On Fri, 9 Aug 2013 00:09:29 -0400
> David Shaw wrote:
>
>> There are two namespaces here. If a tag is defined by the IETF
>> process, then there is no @domain at a
Ok, I see. Probably RIPE server-side software behaves like file(1)
utility(or just calls the file(1) utility), which seems to determine
file as a "PGP public key block" if it contains the "BEGIN PGP PUBLIC
KEY BLOCK" string:
noc@T42 ~/.gnupg $ file pubkey.txt
pubkey.txt: PGP public key block
noc@T
http://dl.fefe.de/gnupg-1.4.14.dif
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
I only replied to Mr. Shaw and not to the list so i send this again.
On Fri, 9 Aug 2013 00:09:29 -0400
David Shaw wrote:
> There are two namespaces here. If a tag is defined by the IETF
> process, then there is no @domain at all. The @domain tags are used
> when regular users want to define a
On Thu, 8 Aug 2013 23:17, eye.of.the.8ehol...@gmail.com said:
> the form t...@my.domain.tld using a domain i own because my meaning
> for "tag" might be different than someone else's. Is this correct ?
Right. For experiments it should be okay to example.com as domain.
If you have a need for a