meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 67 | |
| visits | member for | 1 year, 7 months |
| seen | May 17 at 17:36 | |
| stats | profile views | 1,170 |
I SHALL DEVOUR YOUR HEART AND FEAST ON YOUR SOUL (so don't bug me).
|
Apr 17 |
answered | What are the risk implications of not verifying referer header on login form? |
|
Apr 17 |
comment |
How can police find out about criminal activity on an iPod Touch? This book claims to explain it all. At least, I see no conceptual impossibility in opening the case and reading the Flash chip directly. |
|
Apr 17 |
answered | Is Using MD5 Sufficient Reason to Reject This Payment Processor? |
|
Apr 17 |
answered | Using MD5 for file integrity checks? |
|
Apr 17 |
comment |
Using MD5 for file integrity checks? Technically a second preimage attack, since the attacker also has the genuine file to start with. This is not exactly the same thing as a preimage attack (but close enough). |
|
Apr 16 |
answered | TCP Sequence Prediction and it's prominence in modern systems/networks |
|
Apr 16 |
awarded | network |
|
Apr 16 |
answered | What are security implications of enabling access to performance counters on ARM Cortex A9? |
|
Apr 16 |
answered | What is the distinguishing point between a script kiddie and a hacker? |
|
Apr 16 |
comment |
How to encrypt packets in network? Ethernet is not inherently encrypted. For other network types, anything goes... especially for cable companies, who rarely disclose the nature of the protocols they run over the cable (they want to discourage rogue wiring). It is safest to assume that there is no protection unless you explicitly configured a VPN between the relevant machines. |
|
Apr 15 |
answered | How to encrypt packets in network? |
|
Apr 14 |
answered | Question about HTTPS |
|
Apr 13 |
awarded | hash |
|
Apr 12 |
comment |
Is OpenSSL AES GCM standardized? I did not say that OpenSSL rejects IV longer than 12 bytes; only that NIST recommends that implementations reject IV longer than 12 bytes. Also, the extra bytes are not ignored; they just don't provide additional security benefits. You already have the best security you can hope for with 12 bytes. |
|
Apr 12 |
comment |
Is OpenSSL AES GCM standardized? The actual IV length in GCM is 12 bytes. If the IV is longer, a preparatory step is performed internally, to reduce the IV length. NIST recommends that GCM implementations restrict IV length to exactly 12 bytes. So there is nothing to gain in using larger IV. |
|
Apr 12 |
answered | Is OpenSSL AES GCM standardized? |
|
Apr 12 |
answered | Best practice for securing user credentials once they reach the server using Basic Auth + SSL |
|
Apr 12 |
answered | what is virtual machine introspection? |
|
Apr 12 |
answered | Client code tampering detection |
|
Apr 12 |
answered | SHA256 security: what does it mean that attacks have broken “46 of the 60 rounds of SHA256”? |
