3 ms·
Perhaps. What I mean is, the session id as a bearer token for example can still be insecure even if sent via https. For example, if PHP scripts use $_REQUEST an
by EGreg 9y ago
Perhaps. What I mean is, the session id as a bearer token for example can still be insecure even if sent via https. For example, if PHP scripts use $_REQUEST and session_start() uses the id sent in $_GET from GPC. So you can have session fixation attacks. However, if you additionally require devices to sign all requests with their private key (stored in IndexedDB for the domain and not exportable) then Web Crypto can help mitigate many classes of attacks, including session fixation and CSRF. (It can even increase security over http without https, even though it's an academic point.)
Today we wrote up an article about this, actually, referencing your guide:
https://qbix.com/blog https://qbix.com/blog
It goes into more detail about all this.
- CiPHPerCoder 9y ago> Today we wrote up an article about this, actually, referencing your guide: Neat. I'll have to give that a read in the morning. Although, it looks like one of your links in the opening paragraph under the "Web Security in 2018" header is broken, and presumably that was the one meant to link to our guide.
- EGreg 9y agoWe fixed it :) Lmk what you think.