Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bigmac
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
91.
▲
by
bigmac
16y ago
Maybe its optimistic, but I'd hope this has caused a big enough stir among people running Siemens installations that they are taking care of this issue. If so, that will give it a short lifetime. Even if the individual plant admins aren't
92.
▲
by
bigmac
16y ago
Do you know if it has a command and control component? This author's analysis seemed to indicate that it was relatively simple, which seemed to be why he thought it was so focused. Given that it is going to be easy to patch, it will like
93.
▲
by
bigmac
16y ago
This malware uses four 0day vulnerabilities, stolen device driver certs, and specifically targets industrial control systems. I'll be very interested to see who it turns out was the target of this attack. Some more info here: http://www.s
94.
▲
Analysis of Stuxnet malware (and implication of Cyber Warfare)
(langner.com)
41 points
by
bigmac
16y ago
|
8 comments
95.
▲
by
bigmac
16y ago
I'd be interested in the "considerable time and money" you are talking about. Reading daeken's analysis makes it look like they did not try at all.
96.
▲
First look: Youtube Live Streaming
(wired.com)
1 points
by
bigmac
16y ago
|
0 comments
97.
▲
by
bigmac
16y ago
I wonder if you're right... To the casual observer this seems to undermine the GPL.
98.
▲
by
bigmac
16y ago
Existing java bytecode obfuscators should work. The one I worked on does. The Dalvik compiler translates the .class into dalvik bytecode. You can obfuscate the java bytecode and the obfuscation survives the translation layer.
99.
▲
by
bigmac
16y ago
Perl has taken care to address some of these issues. See 'Algorithmic Complexity Attacks' in perldoc perlsec. For example, the keys of a hash table are guaranteed to be returned in random order, to prevent hash collision attacks on the ha
100.
▲
by
bigmac
16y ago
Also, "love to learn knew things" has a typo with the word new .
101.
▲
by
bigmac
16y ago
Google restates the FTC’s dissection of newspaper revenue: 80% advertising, 17% newsstand, 3% subscriptions. “Pay walls,” it says, “could be an effective way to raise the 3% revenue figure.” Amdahl's Law, anybody? Its not just relevant f
102.
▲
by
bigmac
16y ago
Your problem is real. Vim can do so much that you might not even know that there is a better way. The first step is to realize it will be a slow process. Its doubtful that you'll be able to take time to practice vim for the sole purpose
103.
▲
by
bigmac
16y ago
Bear in mind that the link lists averages across the entire US. Its giving salaries everywhere form Akron, OH to San Diego, CA. Clearly they aren't necessarily top-end Silicon Valley salaries, but people working with security clearances ca
104.
▲
by
bigmac
16y ago
I'm doubtful that anyone with a VP-Level title at BofA is writing software. I have a feeling you're comparing entirely different jobs here. Additionally, Lockheed built (among other things) the SR-71 and the F22. Its probably a safe bet t
105.
▲
by
bigmac
16y ago
There are private sector jobs that require security clearance and pay well. Consider Lockheed Martin, Northrup Grumman, etc. Lockheed on GlassDoor: http://www.glassdoor.com/Salary/Lockheed-Martin-Salaries-E40...
106.
▲
by
bigmac
16y ago
Pleased to see the classic "Smashing the stack for fun and profit." Absolutely essential for anyone in the security industry. Looks like the link is dead; here is a mirror: http://www.phrack.com/issues.html?issue=49&id=14#article
107.
▲
by
bigmac
17y ago
Thomas, have you seen or heard of any real life exploits utilizing return oriented programming? Its a really really cool idea, but it seems that once you've got memory corruption, there are easier ways to get arbitrary code execution than
108.
▲
by
bigmac
17y ago
San Francisco is great. However, I have serious doubts that you'll want to pay for a three bedroom apartment and deal with parking for three cars. Cost being a factor, I wouldn't recommend SF. On that note, why do you need three bedrooms?
109.
▲
Man Buried in Haiti Rubble Uses iPhone to Treat Wounds, Survive
(wired.com)
9 points
by
bigmac
17y ago
|
3 comments
110.
▲
by
bigmac
17y ago
You're correct, the analysis is incomplete without analyzing the payload.
111.
▲
by
bigmac
17y ago
I'd be interested to know which steps of the packaging process were done automatically. Presumably these two could be automated in a straightforward fashion: Embedding a script in a command via cmd /C ... & ... & ... (twice) Gen
112.
▲
by
bigmac
17y ago
Should be able to easily apply to both YC and IO; their application page is definitely inspired by the YC application. http://ventures.io/apply
113.
▲
by
bigmac
17y ago
Interesting that you would say they cross your ethical lines. Their tagline used to be "It is more profitable to be ethical." See: http://web.archive.org/web/20070102022215/http://www.rapleaf...
114.
▲
by
bigmac
17y ago
LLVM. It is a ridiculously well written and well documented codebase. The transformation/optimization framework is remarkable and surprisingly approachable. The compiler intermediate representation is easy to work with both in the emitt
115.
▲
by
bigmac
17y ago
Does this include a config file salt as well?
116.
▲
by
bigmac
17y ago
Arxan Technologies(www.arxan.com) is hiring in West Lafayette, IN. We solve the really interesting problems that tptacek is alluding to here: http://news.ycombinator.com/item?id=953722 Email me (contact info in profile)
117.
▲
by
bigmac
17y ago
He admits as much: "I give credit to the book Brave New World by Aldous Huxley for many of these ideas." He basically presents Huxley's world exactly. His real contribution seems to be the analysis at the end. Specifically, the notion tha
118.
▲
by
bigmac
17y ago
I find the name memorable, at the very least. This must represent some value.
119.
▲
by
bigmac
17y ago
I recently did this exact thing for an upcoming venture -- didn't want anyone beating us to it.
120.
▲
by
bigmac
17y ago
The discussion of the trade-offs between different internal implementations of closures, continuations, and lexical scoping was enlightening. I'd like to hear more about the specifics joys and frustrations of building this all on top of the
More ›