17,855 reputation
1183258
bio website lamontconsulting.com
location New York, NY
age 38
visits member for 3 years, 11 months
seen 44 mins 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


Jul
30
comment Trust Issues Relative to Open Source
@IstvanChung - Thanks, was on a mobile device. Cut&Paste fail
Jul
30
revised Trust Issues Relative to Open Source
added 13 characters in body
Jul
30
answered Trust Issues Relative to Open Source
Jul
29
comment How to trace AD Admin Login
Related: How to trace Admin file creation
Jul
28
accepted What are some examples of a block cipher's versatility over a stream cipher?
Jul
26
comment Do multiplatform viruses exist?
Do XSS and Java / .NET exploits count?
Jul
26
awarded  Popular Question
Jul
25
revised Exchange 2013 blocks txt file attachments - are there security reasons?
deleted 15 characters in body
Jul
25
revised Exchange 2013 blocks txt file attachments - are there security reasons?
added 2897 characters in body
Jul
24
comment Can any ECC field element be safely serialized as “compressed” and then restored as uncompressed?
(love the answer, esp the INAL part) Crazy question, in crypto, does negative zero exist?
Jul
24
accepted Can any ECC field element be safely serialized as “compressed” and then restored as uncompressed?
Jul
24
revised Can any ECC field element be safely serialized as “compressed” and then restored as uncompressed?
added 49 characters in body
Jul
24
asked Can any ECC field element be safely serialized as “compressed” and then restored as uncompressed?
Jul
24
awarded  Popular Question
Jul
24
awarded  Nice Question
Jul
21
comment What considerations should apply for self service Renewing, Revoking, or Unrevoking a certificate?
The password portion is more for the scenario a user can't produce a ZKP. This can happen if they can't find their certificate/smart card or if they lose it at the bottom of the ocean. If they happen to find the smart card, (similar losing their keys and finding them again) I want to permit the user to unrevoke the certificate, but want to prevent a hostile user from doing so.
Jul
21
comment What considerations should apply for self service Renewing, Revoking, or Unrevoking a certificate?
Thank you; for your reference I'm using accumulator-based revocations / unrevocations with ABC4Trust (UProve and Idemix), and Pedersen Commitments to handle when a user is permitted to login (time of day/ day of week). If a prover sends a ZKP to the issuer, then the issuer will authenticate the user and authorize the action for "renew", "good Samaritan revoke".
Jul
21
accepted What considerations should apply for self service Renewing, Revoking, or Unrevoking a certificate?
Jul
21
revised What considerations should apply for self service Renewing, Revoking, or Unrevoking a certificate?
edited title
Jul
20
revised What considerations should apply for self service Renewing, Revoking, or Unrevoking a certificate?
added 151 characters in body