meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year |
| seen | Mar 14 at 10:12 | |
| stats | profile views | 8 |
nothing to report
|
May 19 |
awarded | Nice Question |
|
May 7 |
awarded | Popular Question |
|
Mar 14 |
accepted | How do you get a specific .onion address for your hidden service? |
|
Feb 1 |
answered | Best practices for operating a Bitcoin-Qt client regarding netwok privacy? |
|
Feb 1 |
comment |
How do you get a specific .onion address for your hidden service? someone can imposter your site if they manage to generate the same private key... |
|
Jan 31 |
revised |
How do you get a specific .onion address for your hidden service? added the time needed for calculation |
|
Jan 31 |
suggested | suggested edit on How do you get a specific .onion address for your hidden service? |
|
Jan 31 |
awarded | Scholar |
|
Jan 31 |
awarded | Supporter |
|
Jan 27 |
awarded | Commentator |
|
Jan 27 |
comment |
How do you get a specific .onion address for your hidden service? any idea of how computationally expensive? |
|
Jan 27 |
asked | How do you get a specific .onion address for your hidden service? |
|
Sep 21 |
awarded | Custodian |
|
Jul 6 |
awarded | Cleanup |
|
May 16 |
revised |
PHP - How to do safe input filtering in the light of multibyte encoding vulnerabilities? added 1514 characters in body |
|
May 16 |
comment |
PHP - How to do safe input filtering in the light of multibyte encoding vulnerabilities? the link talks about the utf8_decode, but htmlspecialchars, preg_replace, and other functions have similar issues. If needed I can add links to more vulnerabilities. |
|
May 16 |
comment |
PHP - How to do safe input filtering in the light of multibyte encoding vulnerabilities? Using utf-8 is not a problem, but the problem is that a user might send a piece of text that is not valid in utf-8, or that is downright in some other encoding. As PHP functions like preg_replace treat all text as a byte arrays with each byte representing one character, this can be used to bypass the input filtering. See the sirdarkcat link in my question for a detailed explanation and examples. |
|
May 16 |
awarded | Teacher |
|
May 16 |
comment |
PHP - How to do safe input filtering in the light of multibyte encoding vulnerabilities? Thanks for answering. I will have a look at ESAPI, but this question is about input validation. How would you do input validation if you don't know the encoding of the input? Say I have a file upload and thus need to sanitize a filename. I don't want to whitelist, because not everyone uses an ascii alphabet, so that would be very unfriendly for everyone but english users. I do need to be absolutely sure however that no corrupt or wide character encodings cause something to be interpreted as a slash by the underlying filesystem, otherwise I have path traversel issues. |
|
May 15 |
comment |
PHP - How to do safe input filtering in the light of multibyte encoding vulnerabilities? let us continue this discussion in chat |
