Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 69:30:46 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,240 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
Next to being able to sign messages in echomail/newsgroups,
fully encrypted messages only make sense in email - direct
to a specific individual.
Or routed netmail!
That's the beauty of pulling down the keys and checking
their properties. The properties will reveal creation
dates, expiry dates, revocations, etc. It would be
relatively easy to just pick the most recent date, and send
a brief hello message with a CC: and see which ones reach
their target.
If there are multiple keys to choose from...
Next to being able to sign messages in echomail/newsgroups,
fully encrypted messages only make sense in email - direct
to a specific individual.
Or routed netmail!
But we really don't know the exact route a netmail will take.
For a user, unless they analyze the nodelist or confirm things with
their sysop, netmail is unreliable.
I also use point-software (OpenXP) which allows sending crash mail.
With that, I could crash my encrypted netmail to its final destination with confidence to any system that flies the U,ENC flags.
For a user, unless they analyze the nodelist or confirm things
with their sysop, netmail is unreliable.
Indeed. But I doubt many systems still filter-out/bounce
netmail with encrypted content.
And in case of a point as destination of which the boss has the
ENC flag. You can crash the encrypted netmail at the boss's
system...
For a user, unless they analyze the nodelist or confirm things
with their sysop, netmail is unreliable.
Indeed. But I doubt many systems still filter-out/bounce
netmail with encrypted content.
Now that you let the cat out of the bag, so to speak.. sysops may be interested to add such filters to find out! LOL
Now that you let the cat out of the bag, so to speak.. sysops
may be interested to add such filters to find out! LOL
I don't think our audience is that big.
Now that you let the cat out of the bag, so to speak.. sysops
may be interested to add such filters to find out! LOL
I don't think our audience is that big.
Unless there are publicly disclosed traffic stats on netmail flowing through fidonet, we'll never quite know.
You could do some tests, sending encrypted and non-encrypted routedI may need to set up my Golded to send encrypted netmail, Thunderbird does not allow encrypted mail to "news" netmail...
netmails through the net. But you will have to find volunteer
destinations in all far away corners of the nodelist. ;)
You could do some tests, sending encrypted and non-
encrypted routed netmails through the net. But you will
have to find volunteer destinations in all far away corners
of the nodelist. ;)
I may need to set up my Golded to send encrypted netmail,
Thunderbird does not allow encrypted mail to "news"
netmail...
I posted two test replies in the pkey_drop. One to Wilfred, and one
to you.
You could do some tests, sending encrypted and non-
encrypted routed netmails through the net. But you will
have to find volunteer destinations in all far away corners
of the nodelist. ;)
For starters, the ENC flag seems to be flown in Z2 systems only.
So, it is unlikely that anyone in Z1 would like to participate.
But it could be interesting which non-ENC systems let the messages
pass through.
Nah.. best to stick with known systems that show ENC.
I posted two test replies in the pkey_drop. One to Wilfred, and
one to you.
I posted two test replies in the pkey_drop. One to Wilfred, and one
to you.
The one to me was encrypted only for youself. Very secret. :)
I posted two test replies in the pkey_drop. One to Wilfred, and
one to you.
please remember that PKEY_DROP is only for posting public keys...
..AFAIK, this is the only echo that allows such ;)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 07/01/2020 8:10 a.m., mark lewis : August Abolins wrote:
encrypted and/or signed messsges are allowed in this echo...
AFAIK, this is the only echo that allows such
I recently updated my Win7 pc to TB 68 + the corresponding
Enigmail/GPG plugin.
But signed clear-text email seems to be rolling out with:
gpg command line and output:
C:\Program Files\gnupg\bin\gpg.exe
gpg: invalid armor header: Â \r\n
gpg: invalid armor header: Â \r\n
Signed clear-text messages from other people in this echo look good
and process properly.
So, I am testing one originating from this new TB68/Enigmail combo to
see if the "invalid armor header" is a problem here.
I'd hate to roll back TB. But maybe all I have to do is rollback the Enigmail plugin version?
- --
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc -----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4scOIACgkQ7w6JZVeJ WJugNQf/TcvM1zQJi8hN42CQDCtsTbX0hu2B/Smg3k/zy6aCB5FabIRGxgQCt3C0 yROmIvUpLLwQQ8MMwzYqQfvb25ifmt1NwCNHl2sPSQVeIUQPaU/6PNeikgSNhmXH w7SxK7upP17sAjIY3sG+lOto2S6HgDtt8MVyZrbr4BAUK6EfG475oTsKgo3jezTc ALa2W3tVByYS6TlnvuyqEFJkbShw6ddl+lIclYsK3A8B0y4S+rOLlklUyloUbVY1 u4BBpQAyWXzwLb9Mfm7W/X0pcCzlxCEtn4RXblMg9o7UnVNviYupc31HbLCAo/FO 61EYIA3M6lOe/QCfx6jk62qF+xFNLg==
=iByN
-----END PGP SIGNATURE-----