bitman (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} bitman) wrote,@ 2004-01-27 12:40:00 |
|
Jewelry that plays music
I saw somebody wearing a Rio player on a lanyard around their neck. Music players are getting so small now, I can imagine them being disguised as necklaces. The chain of the necklace can conceal the headphone cords up until either side of the neck. The player itself could be disguised as some sort of gaudy ornament.
I can see this becoming fasionable in the near future. (For guys and girls!) Just you watch.
On a totally unrelated note, I've been having spam problems lately. Somebody's been spoofing my sourceforge address and so I'm getting tons of returned spam, all in Russian. I've got it forwarding to my UW account now, which has excellent filtering, so I only see a few spam a day from there instead of hundreds.
The new W32/MyDoom-A virus has been flying everywhere on the campus networks. I even recieved a copy yesterday. I took a good look at the virus file in less before trashing it (someday I will pay for my complacency -- assuming that using UNIX to read my mail makes me immune to infection). There were some strings like ABCDEF... and 0123456789 in there, and a list of .dll's at the end, but mostly it just looked like binary garbage.
Today I got an automatic message from one of the campus servers telling me that this virus was recieved IN MAIL FROM ME (in caps even). Apparently the new virus .dat files have propogated now. Anyway, the headers indicated that it originated on Qwest's network (phone company -- they do DSL too). I don't use Qwest's internet service, so it wasn't from me. I hate spoofing.
What this needs is a brand new email protocol that (1) requires that you send mail through the server you expect to recieve responses at, (2) verifies the sending server's identity, and (3) requires SSL or future equivalent for all transactions. The first ensures that a mail server can hold its users accountable for the messages they send, the second ensures that other servers can hold the sending server accountable, and the third just makes sense now that we have such good encryption technology.
It would almost certainly have to break compatability with SMTP, but it would so be worth it. POP3 and IMAP would be unaffected.
I saw somebody wearing a Rio player on a lanyard around their neck. Music players are getting so small now, I can imagine them being disguised as necklaces. The chain of the necklace can conceal the headphone cords up until either side of the neck. The player itself could be disguised as some sort of gaudy ornament.
I can see this becoming fasionable in the near future. (For guys and girls!) Just you watch.
On a totally unrelated note, I've been having spam problems lately. Somebody's been spoofing my sourceforge address and so I'm getting tons of returned spam, all in Russian. I've got it forwarding to my UW account now, which has excellent filtering, so I only see a few spam a day from there instead of hundreds.
The new W32/MyDoom-A virus has been flying everywhere on the campus networks. I even recieved a copy yesterday. I took a good look at the virus file in less before trashing it (someday I will pay for my complacency -- assuming that using UNIX to read my mail makes me immune to infection). There were some strings like ABCDEF... and 0123456789 in there, and a list of .dll's at the end, but mostly it just looked like binary garbage.
Today I got an automatic message from one of the campus servers telling me that this virus was recieved IN MAIL FROM ME (in caps even). Apparently the new virus .dat files have propogated now. Anyway, the headers indicated that it originated on Qwest's network (phone company -- they do DSL too). I don't use Qwest's internet service, so it wasn't from me. I hate spoofing.
What this needs is a brand new email protocol that (1) requires that you send mail through the server you expect to recieve responses at, (2) verifies the sending server's identity, and (3) requires SSL or future equivalent for all transactions. The first ensures that a mail server can hold its users accountable for the messages they send, the second ensures that other servers can hold the sending server accountable, and the third just makes sense now that we have such good encryption technology.
It would almost certainly have to break compatability with SMTP, but it would so be worth it. POP3 and IMAP would be unaffected.
