<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: I&#x27;d Sign Up in </title>
<link>http://www.dslreports.com/forum/r7488508</link>
<description></description>
<language>en</language>
<pubDate>Wed, 20 Aug 2008 22:42:02 EDT</pubDate>
<lastBuildDate>Wed, 20 Aug 2008 22:42:02 EDT</lastBuildDate>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7490600</link>
<description><![CDATA[<A HREF="/useremail/u/698757"><b>nixen</b></A> :  <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>And I think it's much more realistic to expect SMTP servers to get certificates than to expect <I>every single user</I> on the Internet to do so. Doesn't it sound cheaper if an ISP only needs one cert per e-mail server, costing a couple hundred a year, as opposed to hundreds of millions of USERS having to get a certficate every year, costing whatever they will cost.<HR></BLOCKQUOTE><br>Sounds cheaper, until you get to the point where you get charged for each and every email address you wish to use. Personally, I use a unique email address for every web site or internet service I sign up for. That way, if I ever receive SPAM at that address, I know who it was that sold my address. That way, I can cease doing business with said service and deadmail the tainted address.<br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Add to that the fact that the requirement to get a certificate to EVERYONE on the Internet would be a nightmare, in and of itself.<HR></BLOCKQUOTE><br>Err... but you're in agreement that everyone should have to authenticate? That everyone should be identifiable? Yet, you don't want to go the next logical step? Besides, personal certificates also mean that you can sign and encrypt your emails (thus upping the privacy of correspondence). It's also a bit more difficult to forge an authentication identity when personal certificates are used.<br><br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>If such a plan caused a lot of 'small' e-mail servers to drop off the face of the planet.. including yours and mine... I'm perfectly happy.<HR></BLOCKQUOTE><br>Ah, one of the people who's perfectly happy to give up a little bit of personal freedom in exchange for a little bit of security, I see. <STRIKE>Fan of the Patriot Act, too?</STRIKE> At any rate, I won't bother to quote Ben Franklin. ;)<br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Hell, I got a server certificate for one of my websites that only has maybe 10 people using it...<HR></BLOCKQUOTE><br>Unless you're selling something off that website and are only doing it to provide an encrypted channel, you'd have been better served generating your own certificate.<br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>After that, ISP's can more pro-actively observe traffic from their users... when users seem to be engaging in 'mass e-mailing',<HR></BLOCKQUOTE><br>Like running a listserv/majordomo, or even something as innocuous as telling everyone in their address book, "we just had a baby," or "I am getting shipped to the gulf," or "I'm moving," (etc.).<br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>the ISP can look closer, and they'll HAVE A USERNAME it's connected to. IT would be up to the ISP themselves to be certain that it's not too easy to simply 'sniff' those usernames over the Internet... perhaps by being certain that SMTP logons don't go OVER the Internet itself, but stay on the ISP's local network.<HR></BLOCKQUOTE><br>So, having given up my ability to have function-oriented email addresses, I'm to also give up my ability to do SMTP transactions as myself, no matter where I am? I mean, what you're proposing means, if I am over at a friend's house who has a different ISP that has such a policy, I am not going to be able to send email (and no, craptacular Web/Mail gateways are not acceptable).<br> <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Given the costs that ISP's claim are associated with handling spam<HR></BLOCKQUOTE><br>And, as an ISP, they're already offloading that cost to the service users (cuz they sure as heck can't offload it to the SPAMmers). What do you think is going to be the real price difference for the end user if mail server choice is <I>reduced</I>?<br><br>Personally I think that everyone that cares about privacy, identity theft, etc., should be screaming for affordable and quickly/easily installed personal certificates. But, that's really a separate issue.<br><br>-tom<br><small>--<br>You can be only -so- accurate with a sledgehammer.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7490600</guid>
<pubDate>Thu, 24 Jul 2003 18:02:49 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7489983</link>
<description><![CDATA[<A HREF="/useremail/u/732377"><b>Marilla</b></A> : I only mentioned POP3 servers because I don't believe any server, at all, that is involved in e-mail should accept any mail that is not 'approved', IF such a system were put in place... I do understand that POP3/IMAP really only deal with delivering the mail to the client.. but.. well, yes.. just remove 'POP3' from my list.. <br><br>And I think it's much more realistic to expect SMTP servers to get certificates than to expect <I>every single user</I> on the Internet to do so. Doesn't it sound cheaper if an ISP only needs one cert per e-mail server, costing a couple hundred a year, as opposed to hundreds of millions of USERS having to get a certficate every year, costing whatever they will cost. Add to that the fact that the requirement to get a certificate to EVERYONE on the Internet would be a nightmare, in and of itself.<br><br>If such a plan caused a lot of 'small' e-mail servers to drop off the face of the planet.. including yours and mine... I'm perfectly happy. Hell, I got a server certificate for one of my websites that only has maybe 10 people using it... certainly, I would get it for my e-mail, OR I would let me ISP get it on their server and make sure they have me set to authenticate to it.<br><br>Actually, my home ISP already DOES require that I authenticate to their SMTP server. I'm sure they wouldn't be concerned about having to get a cert for the e-mail server, <I>if it was being done globally, in order to prevent 'open relays' and other tools spammers can use</I>.<br><br>After that, ISP's can more pro-actively observe traffic from their users... when users seem to be engaging in 'mass e-mailing', the ISP can look closer, and they'll HAVE A USERNAME it's connected to. IT would be up to the ISP themselves to be certain that it's not too easy to simply 'sniff' those usernames over the Internet... perhaps by being certain that SMTP logons don't go OVER the Internet itself, but stay on the ISP's local network.<br><br>Given the costs that ISP's claim are associated with handling spam, I think something like this COULD work... but it would really require a different setup than we have right now, I think...  and it would take a while to get EVERYONE on it, so that it would be effective.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7489983</guid>
<pubDate>Thu, 24 Jul 2003 16:58:02 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7489064</link>
<description><![CDATA[<A HREF="/useremail/u/698757"><b>nixen</b></A> :  <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Of course, it may be too late to really 'tear apart' e-mail and start all over... but one possibility... instead of USERS having to concern themselves with certificates, perhaps ISP's could begin to put in place a system where SMTP/POP3 servers authenticate each other, and SMTP servers become required to perform SOME sort of authentication of their own users, or else they get 'kicked out' of the system, in some way.<HR></BLOCKQUOTE><br><br>Problem isn't really POP/IMAP authentication. Problem is pretty much with SMTP.<br><br>SMTP client authentication is fairly trivial to set up. Unfortunately, just because my SMTP server has authenticated the client, it doesn't really give any other SMTP server a reason to trust anything coming from <I>my</I> SMTP server. For this, you need to set up trust relationships.<br><br>Trust relationships are also fairly trivial to set up (however, depending on the method used, said trust relationships have to trade of scalability and management ease for security). Unfortunately, many people (myself included) don't like to pay hundreds of dollars of year to secure a server with a commercial SSL certificate. It's fairly likely that even fewer are going to want to spend that kind of money on securing a mail server.<br><br>That's why I was suggesting per-user. That way, I could always write my rules such that, if the originating user had authenticated with a certificate from a trusted authority, I wouldn't have to worry about whether I trusted <I>any</I> of the intervening mail hosts. Of course, SMTP would need to pass more than simply "Verify=OK" in the headers - it would need to include the verification certificate fingerprint, or something.<br><br>-tom<br><small>--<br>You can be only -so- accurate with a sledgehammer.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7489064</guid>
<pubDate>Thu, 24 Jul 2003 15:30:48 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7488620</link>
<description><![CDATA[<A HREF="/useremail/u/715380"><b>Maxo</b></A> :  <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Actualy, though, I don't think 'spam' can be tackled - AT ALL - without a substantive change in the whole e-mail system itself. <HR></BLOCKQUOTE><br>Agreed, as great as POP and SMTP have proven to be it's too easy to forge.  On the other hand I think SPAM is as stopable as P2P.  With P2P there's always a bigger nerd out there with too much spare time willing to right a better, harder to stop, program.  With SPAM there's a big enough ass-hole with enough money willing to make a better, harder to stop, program.<br><small>--<br>God I love being a turtle. - Michaelangelo   &raquo;<A HREF="http://www.maxolasersquad.com" >www.maxolasersquad.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7488620</guid>
<pubDate>Thu, 24 Jul 2003 14:48:16 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7488612</link>
<description><![CDATA[<A HREF="/useremail/u/732377"><b>Marilla</b></A> : Yup.. that's why I said it really needs a basic change to the whole system. Our E-Mail protocols were designed for a 'wide open' communication system.. the people that did this weren't expecting things like Spam or e-mail-borne virii.<br><br>Of course, it may be too late to really 'tear apart' e-mail and start all over... but one possibility... instead of USERS having to concern themselves with certificates, perhaps ISP's could begin to put in place a system where SMTP/POP3 servers authenticate each other, and SMTP servers become required to perform SOME sort of authentication of their own users, or else they get 'kicked out' of the system, in some way.<br><br>This could stray into the same sort of 'black listing' system many people fall into now, but what I'm suggesting is an industry-standard method of determining what servers can or can not... bleh... the more I think about this, the bigger headache I get!<br><br>I'll just switch all my e-mail to a 'white list' system, with a 'challenge' mechanism for every possible recepient.<br><br>Ugh]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7488612</guid>
<pubDate>Thu, 24 Jul 2003 14:47:15 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7488508</link>
<description><![CDATA[<A HREF="/useremail/u/698757"><b>nixen</b></A> :  <BLOCKQUOTE><SMALL>said by  Marilla <A HREF="/useremail/u/732377"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Actualy, though, I don't think 'spam' can be tackled - AT ALL - without a substantive change in the whole e-mail system itself. <HR></BLOCKQUOTE><br>If all email was required to originate from authenticated sources and the authentication was made to require the use of third party authentication tokens, then maybe that could work. <br><br>However, paying Verisign (or whoever) to generate me an e-mail key every year is a pain in the ass. Worse, installing such keys into all of your tools is not as simple as just clicking on a certificate installer application. You have to go to each application that you want to authenticate with and install the certificate. Just kinda blows.<br><br>-tom<br><small>--<br>You can be only -so- accurate with a sledgehammer.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7488508</guid>
<pubDate>Thu, 24 Jul 2003 14:35:30 EDT</pubDate>
</item>

<item>
<title>Re: I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7488448</link>
<description><![CDATA[<A HREF="/useremail/u/732377"><b>Marilla</b></A> : I commend your combination of open-mindedness, and yet practical common sense, in that approach.<br><br>Of course, in taking that approach, I think you do understand the basic reality; More than likely, the names on that list will get hit worse than ever imagined possible (I dunno... one day, and 200 mails in my 'Spam' folder on my Yahoo.com address is pretty ugly!)<br><br>Personally, I like an idea that was touched on here in this article; Make the ultimate advertiser responsible for ads they contract for. Of course, we need to be mindful of the possibility that competitors or even just pranksters will 'spam' on 'behalf' of a company, just to cause them trouble... but where we can clearly track a company to having bought advertising from another company with a knowledge that 'spamming' would have been part of it...<br><br>Actualy, though, I don't think 'spam' can be tackled - AT ALL - without a substantive change in the whole e-mail system itself.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7488448</guid>
<pubDate>Thu, 24 Jul 2003 14:29:24 EDT</pubDate>
</item>

<item>
<title>I&#x27;d Sign Up</title>
<link>http://www.dslreports.com/forum/remark,7488383</link>
<description><![CDATA[<A HREF="/useremail/u/698757"><b>nixen</b></A> : But, the address that I'd register would be the one that I use for my <A HREF="http://www.rhyolite.com/anti-spam/dcc/">DCC processes</A>. As such a registered address, it should <I>never</I> receive any emails, SPAM or legitimate. If the address <I>never</I> receives any email for at least a year, then I <I>might</I> consider registering my real address.<br><br>-tom<br><small>--<br>You can be only -so- accurate with a sledgehammer.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,7488383</guid>
<pubDate>Thu, 24 Jul 2003 14:23:39 EDT</pubDate>
</item>

</channel>
</rss>
