meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 4 months |
| seen | yesterday | |
| stats | profile views | 1 |
|
Mar 6 |
comment |
Is it possible to locate Tor/proxy users? Spam is getting on my nerves +1 for "treat as spam rather than TOR problem". captcha will annoy all users, and if the spammer spams manually this wont bother him him too much |
|
Mar 6 |
comment |
Is it possible to locate Tor/proxy users? Spam is getting on my nerves Are you aware of the fact that there are free disposable spam email adresses? (first hit on google: spambog.com/en no affiliation) If the guy knows that, this will have near zero impact. You could of course ask for the scan of an ID or something, but this will get you in trouble with regular users who are pissed by something like that. If there are very distinct spam patterns, why not try to filter posted content by like show a new post as "Currently under review" only if it is hit by the filter. |
|
Feb 6 |
accepted | How to secure a certificate internally |
|
Feb 6 |
comment |
How to secure a certificate internally Thats what I thought. HSM sounds nice, thanks for pointing at that. |
|
Feb 5 |
asked | How to secure a certificate internally |
|
Jan 10 |
awarded | Scholar |
|
Jan 10 |
accepted | How to verify certificate with very little information |
|
Jan 10 |
comment |
How to verify certificate with very little information Jea. Have no idea how hard bruteforce-creating certificates until 48bits of fingerprint match is, but even if 2^48 does sound quite big, it still doesnt feel super secure. But SRP seems to be exactly the right thing for this. :) |
|
Jan 10 |
comment |
How to verify certificate with very little information Thanks, this SRP sounds really good, im gonna look into that. Not true bytes, but 8 characters in base62 (only signs and numbers, should be readable token) which should result in 11 hex-chars or 44bit. Maybe even 12 hex-chars/48bit if base64 is possible. |
|
Jan 10 |
comment |
How to verify certificate with very little information But you still cant verify if the server is the server, so the client registers with the fake server, and then the fake server could act as a client and register with the real server. Not sending over the clientcertificate sounds good, but the problematic situation is before any of this happens. |
|
Jan 10 |
awarded | Student |
|
Jan 10 |
awarded | Supporter |
|
Jan 10 |
asked | How to verify certificate with very little information |
