It's possible to forge headers in certain circumstances. It's not easy. And this is the first time this has happened. It's ridiculously easy to forge email headers. Headers are manually created whenever programmatically sending email messages. That's how messages can be sent from addresses that don't exist, like devnull@example.com or noreply@yourdomain.com. They don't even send a confirmation email that you have to…
You don’t need a password. Posterous fail.
11–20 of 84 posts
Re: You don’t need a password. Posterous fail.
#12It's possible to forge headers in certain circumstances. It's not easy. And this is the first time this has happened. It's ridiculously easy to forge email headers. Headers are manually created whenever programmatically sending email messages. That's how messages can be sent from addresses that don't exist, like devnull@example.com or noreply@yourdomain.com. They don't even send a confirmation email that you have to…
Headers are manually created whenever programmatically sending email messages To clarify this a little, in case anyone isn't familiar, to send an email message programmatically, you basically just send a string with some headers and body content to the email server. Here are what the headers look like: Date: Sat, 13 Jun 2009 06:53:06 -0400 From: Mail Delivery Subsystem Message-Id: To: To change the sender, all you'd…
Re: You don’t need a password. Posterous fail.
#13It's possible to forge headers in certain circumstances. It's not easy. And this is the first time this has happened. It's ridiculously easy to forge email headers. Headers are manually created whenever programmatically sending email messages. That's how messages can be sent from addresses that don't exist, like devnull@example.com or noreply@yourdomain.com. They don't even send a confirmation email that you have to…
As I understand it, they send you a mail telling you about the post and letting you remove it. Not perfect, but probably works 99% of the time.
That doesn't sound like "works 99% of the time" to me, that sounds like an epic fail.
EDIT: It appears that this was more of a configuration issue, so the above only applies if you set up your account this way.
Re: You don’t need a password. Posterous fail.
#14Earlier quoted context omitted.
As I understand it, they send you a mail telling you about the post and letting you remove it. Not perfect, but probably works 99% of the time.
99% of the time? So if someone decides to trash my reputation they can just post a bunch of stupid blog entries as me and it is on me to (a) detect that this even happened by checking my mail, (b) go do whatever work needed to remove the post and (c) try to explain to everyone what happened (likely causing even more people to do it when they realize how ridiculous the system I'm using is) and salvage my reputation? T…
Re: You don’t need a password. Posterous fail.
#15Not so big a deal IMHO. You can always set a pass if spammers start targeting your blog.
http://posterous.com/help/private_sites
"You can set a password on your Posterous site so only the readers you want can see it. To see your site, a user must go to your site url and also enter the correct password for your site."
Re: You don’t need a password. Posterous fail.
#16It's possible to forge headers in certain circumstances. It's not easy. And this is the first time this has happened. It's ridiculously easy to forge email headers. Headers are manually created whenever programmatically sending email messages. That's how messages can be sent from addresses that don't exist, like devnull@example.com or noreply@yourdomain.com. They don't even send a confirmation email that you have to…
As I understand it, they send you a mail telling you about the post and letting you remove it. Not perfect, but probably works 99% of the time.
Re: You don’t need a password. Posterous fail.
#171. Change from "Contributors can post" to "Anyone can post". Counterintuitive, but the first is based on email FROM, the second is moderated.
2. Make a hash as your FROM address. Add it as an alias to send from in Gmail (or whatever you use). Send to posterous from the hash address. Your email address becomes your password.
Re: You don’t need a password. Posterous fail.
#18Of course someone who received an email from the blog owner could use that to fake all those headers but at least it would prevent people posting by simply guessing the email address.
Re: You don’t need a password. Posterous fail.
#19Earlier quoted context omitted.
As I understand it, they send you a mail telling you about the post and letting you remove it. Not perfect, but probably works 99% of the time.
Shouldn't it work oppositely? Prevent the post from appearing until you explicitly approve it from a link in an email.