[32491] in Perl-Users-Digest
Perl-Users Digest, Issue: 3756 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Aug 10 18:09:35 2012
Date: Fri, 10 Aug 2012 15:09:03 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 10 Aug 2012 Volume: 11 Number: 3756
Today's topics:
Re: Netnews for Gen X (Seymour J.)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 10 Aug 2012 09:40:45 -0400
From: Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid>
Subject: Re: Netnews for Gen X
Message-Id: <50250f5d$19$fuzhry+tra$mr2ice@news.patriot.net>
In <86a9y4i655.fsf_-_@gray.siamics.net>, on 08/09/2012
at 07:47 PM, Ivan Shmakov <oneingray@gmail.com> said:
> In this scheme, and taking INN as an example, newsfeeds(5), and
> its reciprocal incoming.conf(5), serve two purposes: they remedy
> the fact that Netnews currently lack autodiscovery (contrary to
> the P2P networks mentioned above), and they code (in a crude,
> but working, fashion) the "trust" relationship between the
> peers.
There's more than trust involved in current news routing; there's also
the ability, e.g., for specific servers to carry only specific groups,
and to announce what they carry.
> With a sound use of digital signatures (and implementing the
> relevant WoT, or re-using the OpenPGP one), we can lay the
> control over what's trustworthy and what's not straight to the
> hands of the user.
I don't see how.
> Let's first assume that "autodiscovery" is in place. Now, Alice
> chooses a "relay" (there may be both free of charge and paid
> ones), and her agent puts (into the distributed hash table, or
> DHT) a (digitally-signed) "pointer" record that all her mail
> should be delivered to that relay.
How do you authenticate a messge from a stranger? With SMTP there's an
unforgable source IP address that I can filter on.
> It makes sense for the Bob's letter to mention a few of his
> previous messages (sent to Alice) in the header.
Not if there are no previous messages.
> Both GNUnet and Freenet (IIRC) implement an HTTP interface, so
> that an ordinary Web browser can be used to connect to the
> network.
Exactly what I want to avoid.
> And what exactly it's for?
The ausit trail in e-mail is intended for diagnostic purposaes, but in
practice it is used for spam filtering as well.
> I don't see why one may need to care /how/ the letter
> has reached its destination if it's a valid and wanted
> one.
There's no automated way to tell that a message is a validated and
wanted one, so you have to rely on heuristics. Deep filtering is one
useful heuristic.
> only a partial solution.
Partial solutions are all we have.
In addition to the difficulty of developing a new infrastructure that
retains the functionality of the existing infrastructure, there's also
the problem of transition.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>
Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spamtrap@library.lspace.org
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3756
***************************************
