Being that it's for a company-sponsored event, I was going to sign up with my business e-mail address. Now that I've taken a look around, that's not gonna happen.
@tylerl I think what @Iszi's getting at is that the restriction probably means that disallowing apostrophes is likely their chosen implementation for protecting against SQLi.
@Ladadadada Like I said, I'm signing up for a company-sponsored activity. So I'm not really going to try much limit testing on the site. That said, if there is a length restriction, it's definitely >20.
If only the server has an electronic certificate (User ID, Version, Public key), how can be possible the encrypted communication between the client and the server?
Is there a web application that checks the TLS capabilities of the browser? At least
supported protocols and versions
certificates
It should create a detailed report of the results. There're good tools for checking server configurations but same tools can not be used to check browser implemen...
I'd usually eat say up to 3 oranges per day the most, when they're good and in season ... but I got me one of those carrying buckets (IIRC over 6 kg) of Sicilian red oranges yesterday and prolly ate half of it
Guys, the disabling of the autocomplete attribute by default has gotten through security review on Mozilla. Please leave a comment on the bug if you don't want this to happen. (@LucasKauffman)
Currently, there is an HTML form/input attribute called autocomplete, which, when set to off, disables autocomplete/autofill for that form or element.
Some banks seem to use this to prevent password managers from working. These days sites like Yahoo Mail seem to do it as well because they feel t...
The OWASP page gives a password field as an example, however the text talks of credit card fields. What do you think of overriding autocomplete=off for username and password fields only? — ManishearthJan 26 at 21:25
@copy two weeks ago I patched in a config option for overriding autocomplete=off, this bug is about making it the default
@Lucas said that a lot of banks use it, and he feels that they should be allowed to continue to use it for both credit card fields (obviously), and password fields (not so obvious)
Anyone else getting "this website does not supply identity information" on HTTPS Twitter? Was it always that way and I'm just now noticing it (shame on me), or is it recent (shame on them)?