17,770 reputation
1183256
bio website lamontconsulting.com
location New York, NY
age 38
visits member for 3 years, 11 months
seen 6 hours ago

The following message is ROT26 encrypted:

SSL isn't good enough. Your website can be hacked.
Help solve the problem by advocating these RFCs:

TLSA (formerly DANE for DNS) Fixes the hackable CA problem

TLS-OBC: Fixes TLS, and the Related Domain Cookie Attack


About me


See ...my LinkedIn profile

Bitcoin: 1Ev4VoQYqZzJa1YvDCyUxFjpFhtK34evHk


Feb
23
revised How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
added 511 characters in body
Feb
23
awarded  Nice Question
Feb
23
accepted Blackberry QNX / Playbook encryption details
Feb
23
revised Encryption and the “security time decay” of prior encrypted data
edited tags
Feb
23
revised How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
added 89 characters in body
Feb
23
answered How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
Feb
23
comment How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
Following on to your bullet point; Perfidies is a Mozilla demo that compares a live browser session against a Plugin vulnerability database.
Feb
23
accepted Protecting websites from outdated browsers and plugins via a whitelist/blacklist combination?
Feb
23
comment How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
Related: Various links to detect out-of-date browsers
Feb
23
awarded  Civic Duty
Feb
22
revised How to prevent cheating (extra votes) in online contests?
deleted 6 characters in body
Feb
22
revised How to prevent cheating (extra votes) in online contests?
added 105 characters in body
Feb
22
revised Role Based Access Control + Data Ownership based permissions
edited title
Feb
22
answered Role Based Access Control + Data Ownership based permissions
Feb
22
comment Whitelisting DOM elements to defeat XSS
Your link says that it's the "old and crusty" version of CSP. I think the new one is at the w3c: dvcs.w3.org/hg/content-security-policy/raw-file/tip/…
Feb
22
comment How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
@DW I realized I didn't formulate my question correctly. I've changed it substantially. See my comment to Avid above. Originally, I was attempting to re-purpose your answer for securing images in my first question to general documents since I thought they can be exploited with similar mechanisms (depending on the software and "trust zone" involved).
Feb
22
comment How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
@AviD I was getting ahead of myself, and did this Jeopardy style. My underlying question is "how to I secure document transmission over the web", my assumed answer was to "convert it into a "Safe" format". I've edited the question; do you think I altered it too much and had best delete it and start over?
Feb
22
revised How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
deleted 1003 characters in body; edited title
Feb
22
revised How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
added 428 characters in body; edited title
Feb
22
comment How should I serve untrusted / unsanitized documents (PDF, DOC, XLS) to end users over the web?
@GeorgeBailey - I'm ultimately looking for a conversion exe that can run locally or on a server, and has some programmatic interface I can leverage. Lacking that, I'll suffice with command line switches. (If the TOS permits, I may wrap the Google Docs service into an EXE)