5 ms·

Posterous really does fail here. I can see why they would want to tolerate a little of this to preserve ease of use for their users (just like Amazon with their

by tman 16y ago

Posterous really does fail here. I can see why they would want to tolerate a little of this to preserve ease of use for their users (just like Amazon with their Kindle email address). However, there are a number of steps that Posterous can take to combat forged headers in ways that should not impact users at all. Enabling SPF, for example, would be a good start. Technically, it's the same problem as email spam, and most of the same tools can be used to combat it. Posterous should flag posts that they aren't sure of and make users confirm them before putting them up, etc. EDIT: The other fix would be to use an email address that can't be guessed from the blog address. In other words, the email address is the password.

axod 16y ago
> "The other fix would be to use an email address that can't be guessed from the blog address. In other words, the email address is the password." You'd still be sending your password in the clear, possibly through other peoples mail servers. Not great security.
- tman 16y ago
  The perfect is the enemy of the good. There is a trade-off here between security and usability. 99% security is good enough for a lot of purposes and has its place.
  - infinite8s 16y ago
    Except that's more like 10% or 1% security.
  - infinite8s 16y ago
    Except that's more like 10% or even 1% security.
    - tman 16y ago
      Oh really? I don't think you know what you mean. In point of fact, I just sent myself a very important password in clear text. Hack me.
      - axod 16y ago
        The task for a spammer isn't to hack <USERS> account. It's to hack ANY account. Being able to hack any posterous account is going to be far far easier than trying to hack a particular account.
prakashk 16y ago
> The other fix would be to use an email address that can't be guessed from the blog address. In other words, the email address is the password. Multiply (http://multiply.com http://multiply.com) does something similar. You set your post-by-email id. And, then email your posts to the post-by-email-id@your-multiply-id.multiply.com. You decide how complicated or easy you want your post-by-email-id to be. As someone said, this is not 100% secure as the email address is sent as clear text as it passes through mail servers, but it's more difficult for someone to guess it. They do perform additional checks on the message sent to make sure it came from you, perhaps similar to those that Posterous does.

by tman 16y ago

axod 16y ago

> "The other fix would be to use an email address that can't be guessed from the blog address. In other words, the email address is the password." You'd still be sending your password in the clear, possibly through other peoples mail servers. Not great security.

tman 16y ago
The perfect is the enemy of the good. There is a trade-off here between security and usability. 99% security is good enough for a lot of purposes and has its place.
- infinite8s 16y ago
  Except that's more like 10% or 1% security.
- infinite8s 16y ago
  Except that's more like 10% or even 1% security.
  - tman 16y ago
    Oh really? I don't think you know what you mean. In point of fact, I just sent myself a very important password in clear text. Hack me.
    - axod 16y ago
      The task for a spammer isn't to hack <USERS> account. It's to hack ANY account. Being able to hack any posterous account is going to be far far easier than trying to hack a particular account.

prakashk 16y ago

> The other fix would be to use an email address that can't be guessed from the blog address. In other words, the email address is the password. Multiply (http://multiply.com http://multiply.com) does something similar. You set your post-by-email id. And, then email your posts to the post-by-email-id@your-multiply-id.multiply.com. You decide how complicated or easy you want your post-by-email-id to be. As someone said, this is not 100% secure as the email address is sent as clear text as it passes through mail servers, but it's more difficult for someone to guess it. They do perform additional checks on the message sent to make sure it came from you, perhaps similar to those that Posterous does.