Skip to main content
Information Security
D.W.'s user avatar
D.W.'s user avatar
D.W.'s user avatar
D.W.
  • Member for 13 years, 11 months
  • Last seen this week
Profile Activity
Stats
100,311
reputation
10.4m
reached
1,023
answers
121
questions
Communities
View all
Badges
View all badges
33
gold badges
279
silver badges
604
bronze badges
Top tags
View all tags
1,359
Score
145
Posts
13
Posts %
1,299
Score
159
Posts
14
Posts %
1,217
Score
149
Posts
13
Posts %
1,053
Score
117
Posts
10
Posts %
1,030
Score
111
Posts
10
Posts %
811
Score
121
Posts
11
Posts %
Top posts
View all questions and answers
answer
165
Why would someone trust DuckDuckGo or other providers with a similar privacy policy?
Mar 13, 2012
answer
114
Is it generally a bad idea to encrypt database fields?
Jul 7, 2012
answer
93
Can anyone provide references for implementing web application self password reset mechanisms properly?
Jan 30, 2011
answer
92
Are URLs viewed during HTTPS transactions to one or more websites from a single IP distinguishable?
Jun 7, 2011
answer
84
How to achieve non-repudiation?
Aug 11, 2011
answer
79
Should I use AntiForgeryToken in all forms, even login and registration?
Feb 12, 2011
answer
78
Can wiped SSD data be recovered?
Mar 7, 2012
answer
78
Is Django's built-in security enough?
Jan 10, 2013
answer
77
Is HTTP compression safe?
Sep 20, 2012
answer
75
Lessons learned and misconceptions regarding encryption and cryptology
Feb 20, 2011
Top Meta posts
13
37
19
Are the wrong questions and answers getting too many upvotes?
16
Downsides of migrating questions from high-volume sites
9
How do you avoid answers with subtle security flaws?
9
Blocked by SmoothWall
8
Another debateable migration
Top network posts
View all network posts
220
Please upload DMCA takedowns to the Chilling Effects Clearinghouse / Lumen Database
189
Why do we count starting from zero?
172
Statement from SO: June 5, 2023 Moderator Action
163
Should we trust the NIST-recommended ECC parameters?
131
How to fool the "try some test cases" heuristic: Algorithms that appear correct, but are actually incorrect