Timeline for Client side authentication through signatures instead of passwords
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2016 at 1:35 | comment | added | Robert Harvey | What happens when someone begins tampering with the actual Javascript/HTML? How does TLS help you there? | |
| Aug 13, 2016 at 10:23 | comment | added | David Spector | I agree with your comments. TLS does it right, and you don't want bugs to compromise security. The Let's Encrypt project is bringing free and universal TLS to the Web. Note that current TLS implementations are actually faster than non-encrypted connections. | |
| Aug 12, 2016 at 4:09 | comment | added | Chris Cirefice | There is no excuse for not using TLS (SSL). If you don't encrypt connections to your web site, users will inevitably be targeted, lose trust in your service, and potentially sue your company for negligence. I have not heard of a web framework that doesn't support TLS. Use it, even if you don't want to. | |
| Jun 12, 2016 at 22:10 | review | Late answers | |||
| Jun 13, 2016 at 7:44 | |||||
| Jun 12, 2016 at 21:54 | history | answered | David Spector | CC BY-SA 3.0 |