freejack

32 ms·

1. 301.▲
   by freejack 15y ago

   Thanks - there was really no discussion on that particular aspect of the implementation :-)
2. 302.▲
   by freejack 15y ago

   The short form is that we pulled our plans ahead based on all the great feedback we received this week and implemented exactly what we should have done months ago. We used bcrypt. We used bcrypt. We used bcrypt. We used bcrypt. We used bcry
3. 303.▲
   Hover secures passwords with bcrypt and adds ID verification(help.hover.com)

   16 points by freejack 15y ago|4 comments
4. 304.▲
   by freejack 15y ago

   I don't disagree with most of what you are saying, and would add that good security practice is a shared responsibility. Sharing passwords across sites is the user equivalent of storing passwords in plain text. i.e. It might be secure enoug
5. 305.▲
   by freejack 15y ago

   Industry secret - at the most basic level, registrar and registry staffers don't need access to a customer account to manipulate a domain name. We've implemented tons of controls to manage who can do what, etc. but relying on customer passw
6. 306.▲
   by freejack 15y ago

   There was a bit more to it than that, but on this specific point, lesson well learned. I rushed this instead of looking for an agreement - as they say, measure twice, cut once.
7. 307.▲
   by freejack 15y ago

   Most of our customer inquiries come in over the phone.
8. 308.▲
   by freejack 15y ago

   Thanks for the note. We're lining up to knock this out quickly. Drop me a note to ross@hover.com if you like and i can fire you an update when we update password security and the rest of the related tools. We can set you up with a corporate
9. 309.▲
   by freejack 15y ago

   Nope, this issue is uniquely ours and has nothing to do with OpenSRS. I usually try not to speak for them, but I can say authoritatively that this simply isn't the case.
10. 310.▲
    by freejack 15y ago

    Absolutely.
11. 311.▲
    by freejack 15y ago

    "why would your team not opt for things that ARE vetted as being secure, trusted, open, and have widespread adoption?" It was a classic case of letting product management opinion over-ride engineering implications. Namely, on behalf of cust
12. 312.▲
    by freejack 15y ago

    tl;dr: guy from hover, mea culpa, new code on the way. I thought it might help to provide some further deets on that blog post. I don't think we're making a case there, or providing an excuse - it certainly wasn't my intent to try and convi
13. 313.▲
    by freejack 15y ago

    Not sure I buy it. The advice implies that Twitter is a broadcast medium - which is only true to a point. Twitter is way more useful as a conversation medium where everyone can eavesdrop. So yeah, talking about lunch isn't always the most p
14. 314.▲
    by freejack 15y ago

    Apple gets a social messaging backplane for essentially free while Google struggles with building their own. Strategically this puts them ahead of GOOG and AMZN and on better footing with Facebook. Apple has previously tried to do a deal wi
15. 315.▲
    Casualty of the first bubble poised for a comeback?(realnames.com)

    1 points by freejack 15y ago|0 comments
16. 316.▲
    by freejack 16y ago

    More like "Godaddy competitor tries to capitalize on PR stumble with thinly veiled promotional campaign"
17. 317.▲
    by freejack 16y ago

    There are lots of stupid startups. Why would the ones behind these top-level domains be any different? ICANN's role isn't to pick the winners, its to manage the overall framework. Perhaps .sex will succeed where .xx fails. Or not. But you c