Jargons of Info Tech industry

axel at white-eagle.invalid.uk axel at white-eagle.invalid.uk
Tue Oct 11 16:27:30 CEST 2005

In comp.lang.perl.misc Roedy Green <my_email_is_posted_on_my_website at munged.invalid> wrote:
>>HTML is a problem on *other* peoples crappy software as well. It
>>wasn't designed to carry code content, but has been hacked up to do
> It seems to me it goes without saying that you cannot trust code from
> strangers, especially anonymous strangers.  You simply don't run code
> sent in email except from highly trusted individuals.  If you do, that
> is YOUR fault for being such a silly ass not the mail system's ability
> to deliver code.  It is as stupid as running code that came as an
> attachment.
> One of the ideas I play with in my essay  is that you could insist
> your correspondents have digital id certificate signed by Thawte or
> other CA attesting to their identity, thus giving you legal recourse
> against them if they send you spam, Trojans etc.
> This would slow them down with requests for permission to send. they
> could send only one per certificate.  The  cost and hassle of getting
> the certificate could deter tem, and uniquely identify them for
> blocking and public black lists.

Plus being a total pain for legitimate correspondents and also expensive.

I don't know how much spam other people receive but on one account I
hardly receive any as I reserve it for friends and business. On another
I had about 40 spam messages which took all of ten seconds to delete.
Hardly a serious matter.



More information about the Python-list mailing list