3 ms·
Your 2nd point has significant performance implications, so I wouldn't take that for granted. Your 1st point is pretty controversial and has significant UX imp
by wahnfrieden 14y ago
Your 2nd point has significant performance implications, so I wouldn't take that for granted.
Your 1st point is pretty controversial and has significant UX implications. Using OpenID instead of just the built-in Django auth or bcrypt is hardly "much much easier" either, it's far more complex to integrate.
- jmathai 14y agoI don't think the 2nd point has significant performance implications. If you're not serving up static pages then there's always network calls to be made on the backend. Storing a nonce on the client and looking everything up on the backend is an easy solution which means you don't have to worry about what data you're storing and if that'll be available in the browser. I think it's cheaper to optimize on the backend for a simpler (and safer) solution.
- lifeisstillgood 14y agoThank you - my thoughts too I cannot trust anything returned from a client so it seems best to Only return one thing from the client As for a carefully vetted security pro - that's great but I am looking for basic generic best practises (we know that has evolved from md5 hashes to bcrypt but what else is there?) It seems either a hole in my education or a hole in general common knowledge
- ivix 14y agoI think the point of a framework like django is that the defaults are best practices. It's good to understand why it does the things it does, but without a certain amount of trust in the framework, you can lose a lot of it's advantages.