OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
G0TEZ  > PGP      06.07.02 13:12l 38 Lines 1591 Bytes #999 (0) @ WW
BID : 15_G0TEZ
Read: DB0FHN DG8NGN GUEST DL7NDR
Subj: public-key.ASC, how?
Path: DB0FHN<DB0ZWI<DB0CHZ<OK0PKL<OK0PPL<RZ6HXA<SP7MGD<GB7YKS<GB7YFS<GB7COV<
      GB7MAX<GB7SAM<GB7OAR<GB7BOB<GB7HVU
Sent: 020630/1330Z @:GB7HVU.#16.GBR.EU #:29244 [Great Harwood] FBB7.00i $:15_G0
From: G0TEZ@GB7HVU.#16.GBR.EU
To  : PGP@WW

G0TEZ/TPK 1.83c Num 15  30-06-02T11:41:49 GMT: COLNE,Lancs:

Hello and thanks for eading this.

I recently dug out a floppy containing pgp2.6.2i. Among other things it
contains public keys in the format callsign.ASC.

I can't find anything in the docs about how to create a G0TEZ.ASC.
I've tried the -kx option without sucess. I would appreciate a litle help.
The floppy dates back to when people were signing packet messges with a
pgp signature. I think that sysops decided that, even with a public key,
this was breaking the rules on encryption so it never caught on.

My reason for abandoning the programme was that I didn't have enough HDD
space back then, whereas my 1.6GB on this PC means it can sit there and
only take up a fraction of the drive. I do know that the US version of
pgp under another name is automatically used when sending secure internet
info so all I'm doing is just playing with it. I also have a directory with
some stega-stuff in it which I couldn't use for the same reason back then.

One station, who's callsign I forget, did send out a picture in .GIF format
which turned out to contain a message and that's how I found out about
steganography because he told a few people by SP what he had done.

I'm not considering sending out any encrypted stuff on packet by way of
steganography or anything else, I've always got email for that.

I just feel like a play and it's rather annoying that I can't remember how
to extract my public key to a .ASC file so, if anyone can help I would
be grateful.

All the best. Ian.




Read previous mail | Read next mail


 17.09.2025 05:12:30lGo back Go up