Timeline for Alternatives to basic and digest authentication in HTTP when resources are constrained
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2017 at 10:08 | history | edited | schroeder♦ | CC BY-SA 3.0 |
added 63 characters in body; edited title
|
| Jul 4, 2017 at 9:42 | history | edited | TrinityTonic | CC BY-SA 3.0 |
added 73 characters in body
|
| Jul 4, 2017 at 8:50 | comment | added | dandavis | you can use another server w/https to login, then talk to your site from that server, which at least eliminates "coffee shop" password vectors, even if behind the scenes where few have access it's in the clear. | |
| Jul 4, 2017 at 8:27 | answer | added | Serge Ballesta | timeline score: 1 | |
| Jul 4, 2017 at 8:13 | comment | added | Jacco | If you can guarantee the integrity of both client and server software, you could take a look at SRP, but I doubt you can get secure communications going without spending the necessary resources to enable encryption, whatever the setup. | |
| Jul 4, 2017 at 7:52 | history | asked | TrinityTonic | CC BY-SA 3.0 |