jwcrux

12 ms·

91.
by jwcrux 10y ago
Nice! I did something similar with the San Antonio Police Department open data: http://jordan-wright.com/blog/post/2016-05-06-exploring-sapd...
92.
by jwcrux 10y ago
This doesn't really explain what it's checking, but if you're looking for an actual checker for your HTTPS configuration, Qualys SSLLabs maintains an open source client [0] that could easily be scripted to do this exact thi
93.
by jwcrux 10y ago
I love this quote: "the plural of anecdote is not data"
94.
by jwcrux 10y ago
https://github.com/showcases/projects-with-great-wikis
95.
LastPass Security Updates(blog.lastpass.com)
2 points by jwcrux 10y ago|0 comments
96.
Breaking PHP’s Garbage Collection and Unserialize(evonide.com)
3 points by jwcrux 10y ago|1 comments
97.
by jwcrux 10y ago
I do work for Duo, and thanks for the suggestion! Much appreciated! I'll bring it up to the team.
98.
Show HN: Insight – A Simple, Completely Free Phishing Assessment(insight.duo.com)
12 points by jwcrux 10y ago|2 comments
99.
by jwcrux 10y ago
"infected" is the industry standard. IIRC (could be making this up) gmail knows to try "infected" in password protected zips.
100.
How to Keep Calm and Mitigate a 470 Gbps DDoS Attack(incapsula.com)
1 points by jwcrux 10y ago|0 comments
101.
Analyzing 4.3M Police Call Records(jordan-wright.com)
1 points by jwcrux 10y ago|0 comments
102.
by jwcrux 10y ago
How often is File Locking needed? I thought that was one of the beautiful things about Git - merging de-conflicting is not only a thing, but easy to do...
103.
Analyzing 5 Years of Police Call Data(jordan-wright.com)
4 points by jwcrux 10y ago|0 comments
104.
by jwcrux 10y ago
Exactly. It's crappy that they are likely getting flack over this. Chances are, it was leaked by a disgruntled employee. But the fact is that the red team started on the internal network and used tactics that would work on darn near e
105.
by jwcrux 10y ago
Yes, this was one of the 9+ vulns they found.
106.
How the Top 5 OEMs Open Your Laptop to Hackers(wired.com)
1 points by jwcrux 10y ago|0 comments
107.
by jwcrux 10y ago
That's what happens when you compromise a site that you don't have authorization to test. You always run this risk when performing testing that isn't under the umbrella of a formal bug bounty.
108.
The Full Story Behind Bloomberg's Attempt to “Unmask” Zero Hedge(zerohedge.com)
2 points by jwcrux 10y ago|0 comments
109.
“Badlock” Details Have Been Released(badlock.org)
1 points by jwcrux 11y ago|0 comments
110.
I Automated “Thought Leadership”, and It's Hilarious(jordan-wright.com)
4 points by jwcrux 11y ago|0 comments
111.
I Automated Infosec “Thought Leadership”, and It's Hilarious(jordan-wright.com)
1 points by jwcrux 11y ago|0 comments
112.
by jwcrux 11y ago
Might be DNS issues? I'm with TWC and DNS isn't resolving.
113.
by jwcrux 11y ago
Needs "Essential Debugging with print statements"
114.
What Happens When Tor Exit Nodes Break Bad(jordan-wright.com)
3 points by jwcrux 11y ago|0 comments
115.
What Happens When Tor Exit Nodes Break Bad(jordan-wright.com)
1 points by jwcrux 11y ago|0 comments
116.
by jwcrux 11y ago
Like others have said, pre-commit hooks for linters are very helpful. Also, CI is a must . These alone can significantly speed up code review since you can be fairly confident you won't break anything new. Then, you just have to focus
117.
by jwcrux 11y ago
Just a heads up, the header on the security page [1] says "SSL and TSL". I see later on that you correctly say "TLS", but mistakes like that in headings don't spur confidence :) [1] https://www.charliehr.
118.
TrendMicro: A remote debugger stub is listening in default install(bugs.chromium.org)
10 points by jwcrux 11y ago|0 comments
119.
by jwcrux 11y ago
This is awesome. I have a repo with only about 1k stars, so nowhere near the adoption of something like npm, etc. Even on my repo, I still regularly receive issues that say "it doesn't work. Why?" With no reproducable info. T
120.
by jwcrux 11y ago
I'm not a JS dev, but would it be possible for a malicious actor to create a pre/post install script that looks for packages published by the current user and "worms" its way into those pre/post install scripts? If

More ›