Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix typo #1

Closed
wants to merge 1 commit into from
Closed

fix typo #1

wants to merge 1 commit into from

Conversation

nshalman
Copy link

@nshalman nshalman commented Apr 9, 2014

No description provided.

@xkill
Copy link

xkill commented Apr 9, 2014

+1

1 similar comment
@PHPGangsta
Copy link

+1

This was referenced Apr 10, 2014
@nshalman
Copy link
Author

Fixed by @decal in 2482126

@nshalman nshalman closed this May 12, 2014
@nshalman nshalman deleted the patch-1 branch May 12, 2014 19:49
@nshalman nshalman mentioned this pull request May 12, 2014
@decal
Copy link
Owner

decal commented Aug 31, 2014

Wow, what a mess. I put it there on purpose as an anti-skid countermeasure during the dawning days cause I didn't want anything crazy stupid happening because of me. The reality was that it was beyond me cause so many different attack modules were going after it. I guess the syntax is fine now.

@decal
Copy link
Owner

decal commented Aug 31, 2014

At this point, I'm only interested in a one-piece super-exploit that dumps the leaked memory and isolates the private key for both server-side and client-side TLS, DTLS and STARTTLS (if it exists.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants