HNHacker News
TopNewBestAskShowJobs

micaksica

1,719 karma · joined January 26, 2016

i work on web application security.

american west coast / singapore / 東京

the opinions expressed here are my own and not the opinions of my employer. they might not even be my own professional opinions. they are also subject to a lot of change, as they have through the years.

submissionscomments
micaksica··on Alleged hacker Lauri Love to be extradited to US
> But for some reason every politician's reaction to cyber events is to make the CFAA more draconian.

I forget who said this, but it's because to a lot of this generation of politicians, a lot of "hacking" and "cybercrime" is a modern-day witchcraft. Aside from a few allies in Congress, technological aptitude (and those that actually understand cybersecurity) will likely lag until a lot of these older career politicians are replaced by "digital natives".

It's not just politicians, either. Some execs at non-tech companies respond to penetration tests in the same way. "How did you do that?" "Why is this possible?" It's just completely outside of their realm of knowledge, and they trust their systems to be as failsafe as most mechanical ones.

micaksica··on Old Geek
> Making generalizations from a set of interviewees is very risky - because interviewees are very, very different from the general population.

While I agree with this statement, the ageism I think is plaguing the Valley is an interviewing/HR/hiring issue, as it is in that process that their confirmation bias is being reinforced there when they bring the old dogs through the door.

FWIW the best engineers I have ever worked with, in my opinion, always seem to be the ones ten years or so ahead of where I am. They're the ones I am always learning something from.

micaksica··on Old Geek
Oh, I agree. I think there is a definite issue of people ascribing "old dogs, old tricks", and that bias is the hard thing to overcome. It's especially hard when a lot of people are confirming that.

It's the age equivalent of https://xkcd.com/385/ . When it's a younger person, it's "this person can't code for <x> because they don't have experience." It's harder to quell that cognitive dissonance when you don't have that out and forces you to place the blame on incompetence.

micaksica··on Old Geek
> Yeah, for the vast majority of engineering programming is like selling shoes. You just need about 4 years experience and you pretty much know it all.

That's the point I'm trying not to make. Are you building a startup that's effectively a CRUD app? If so, sure, that's pretty much all you need and is why coder schools have become so prevalent - they get you to a practicing point that covers the bases of most small websites and very, very basic startups.

Age and experience brings with it something vital: the ability to build long term pattern recognition of technology business cycles, the "all is old is new again", the ways that novel technologies may fall like their predecessors. This is not something you learn in a CS program or even a few years out of college. It's something you only learn by playing with tens of languages and mastering six or seven over decades, by constantly learning, by being part of those business cycles. This skillset is often discredited and is enormously valuable, but I believe it requires a tireless passion for novelty and modern technique to become a multiplier on skill.

micaksica··on Old Geek
I am not really "old" (ie over 40), but I have interviewed older candidates for some technical roles at very different companies, and I've found there are either old people who believe they know better at everything whose skills have not improved much since their early 30s, and then old people who stay up to date on technologies, trends, and realize that programming is a field you never really ever master with time or age; it shifts too much to be able to ever fully grasp it.

The "old" people who are curmudgeonly and stuck on older technical stacks are the ones who don't fare well. The ones who are current in skillset never seem to have an issue and generally impress the people they meet, as they bring both experience and current technical knowledge to the table. Anecdotally, I would say 8/10 of the 40+ crowd I have interviewed fall into the "old technical stack" / "i know better" crowd, and I think these are the ones that poison the well for the good guys.

I am beginning to believe that the trick to software engineering as a career vs. management is to stay current above all else. If you let yourself become obsolesced, you will be thrown aside like an old PowerBook. That's the reality of the technology industry and has little to do with age.

micaksica··on Tor’s Branding Pivot Is Going to Get Someone Killed
> It is sad to watch the Tor Project implode.

I don't see this as an implosion. I am not fond of the majority of SJW rhetoric as a lot of the defenses seen in those circles seem to be constructed as thought-terminating cliché.

I have much respect for Virgil, but I also think Tor is in need of a rebrand at home.

Ancap/cypherpunk messages are not agreeable to the mainstream, and they do not maintain a project when it becomes this close to mainstream. The common Western observer begins to equate the network with the abusive practices inherent in anonymous communication. The average user sees "Tor" and thinks "child porn" or "drug dealers", or "Mr. Robot" hacker types. These are things that economic resources that have to answer to Western political authorities will run from, and if the project needs funding, it needs to have a feel-good message that supporters can parrot to politicians and others that actually have power.

I, too, am an anarchocapitalist cypherpunk type. But I'm realistic enough to recognize you can only push that platform so far as an organization scales. Most people still won't care.

Full disclosure: I am not affiliated with Tor, but I have run relays in the past and will likely run more in the future.

micaksica··on "fs" unpublished and restored
Because for a good chunk of the "web developer" or "web programmer" community, Node.js leverages the HTML/CSS/JS skillset they already have honed writing WordPress plugins and themes.

It's easier to get adoption of your platform when it's a syntax one-trick-pony mom and pop "website design" companies understand, because now with some tutorials they can say that they, too, can write server side code.

micaksica··on Priorities in security
I agree with tptacek here. The common enterprise CISSP I've met seems to have an authoritarian streak, sure. A lot of the ones that work in or were trained by the intelligence community, obviously. But a good chunk of the security engineers and vulnerability researchers I've met have a strong distaste for the authoritarian structures, arbitrary hierarchies, and in some case the concept of the state itself.
micaksica··on NSO Group's iPhone Zero-Days used against a UAE Human Rights Defender
> armed men with carbines will show up and ransack your offices and home

This is a solid reminder that in the end, your ability to use defensive technology does not actually decide who calls the shots. Power is still ultimately controlled by violence.

micaksica··on NSO Group's iPhone Zero-Days used against a UAE Human Rights Defender
The UAE really hates on activists, and appears to be hiring a bunch of people specifically to suppress activists/dissidents within the country. [1] Unfortunately, due to the amount of wealth the country has, it won't stop almost anybody from dealing with them unless Western sanctions are placed on the country, which are unlikely given the current geopolitical situation.

https://www.evilsocket.net/2016/07/27/How-The-United-Arab-Em...

micaksica··on The alleged NSA malware developers are at risk to be identified
Agreed. There are probably 5-25K (yes, large range, but still order of magnitude higher) people in the Bay Area alone that are capable of writing exploits.
micaksica··on The alleged NSA malware developers are at risk to be identified
Awesome. Thanks for this. I missed this one.
micaksica··on The alleged NSA malware developers are at risk to be identified
This post seems lacking in the data required to make such a claim; I do not understand how it has gained so much traction.

Where is the actual research, and where are the probable identified candidates? Did I miss a data analysis part somewhere that explained the methodology, and probable attribution to actual people? This appears to be a basic string search of the code and some simple syntax analysis.

There are learning algorithms for stylometry, and they can probably be adapted to code. This article appears to state that "it might be possible to use these anomalies as clues", but does not elaborate on, how, why, or what any hypothesis is other than this.

micaksica··on “Node.js is one of the worst things to happen to the software industry” (2012)
> The amount of knowledge to be good at all of this far surpasses the "oh, they only know javascript" naivety that I hear from other developers.

No, that's not it at all. I am friends with front end guys and I'm aware at how much work it takes to just keep up with and be good at the framework du jour, Backbone or Angular or React (then Flux, then Redux) and whatever's next from there.

Being good at markup and layout, and being good at a front-end framework, are not skills that are direct analogues to systems-level issues that plague Node.

For example, Node LTS's Buffer() uses UInt8Array on the browser, but a malloc() on the server side that may return insecure memory with leaked information from other parts of the process. libuv's event system is written in C. Socket programming on -nix is nothing like using a WebSocket library in Chrome, and the front-end has no concept of filesystems outside of localStorage or limited WebSQL use. When was the last time a browser had you deal with malloc()?

How many front-end developers understand the performance of writing files to disk with different filesystems, master-slave or master-master replication of databases, building solid server-side deployment workflows, securing their code and their servers from all the things that can go wrong? This skillset generally doesn't exist; it's abstracted away by the Chromium sandbox, or the interpreter. Front-end generally does not require knowledge of the principles of the underlying operating system and architecture to get the job done.

On the backend, all of these problems become apparent. It takes a different way of thinking, and a different understanding of a computer system. My original comment to rdtsc is just that -- a "JavaScript" developer that works on front-end tech only doesn't have an adequate idea of how these things work to build good server-side architectures, and Node.js is not the tool to use for those types of things.

Frankly, if they only know JS, they haven't touched these things at all. Outside of Node and Electron, virtually nothing on a system outside of a browser is written in JS, so you wouldn't have picked up these systems skills in JavaScript.

micaksica··on “Node.js is one of the worst things to happen to the software industry” (2012)
> If there is a team of developers that just know Javascript and nothing else. Then perhaps it makes sense to have a Node.js project. Keep it small and internal.

If you have a team of developers that know just JavaScript and nothing else, you are probably dealing with 100% front-end developers that have little to no understanding of systems programming and what you need to do to be performant and secure outside of a browser.

This leads to a lot of issues with security in the Node.js ecosystem, and is one of the reasons I have a job.

micaksica··on Justice Department says it will end use of private prisons
> I find the hypocrisy astounding when the far right in this country is hell-bent on pushing their religious beliefs into our laws and government policies (abortion, birth control, marriage, etc).

While I have met many Christians in America that do live by their beliefs, I have found the majority of these self-professed "Christians" I have met are simply using the term as a tribal banner in which to wage a cultural war that enriches them and continues their evolutionary propagation at the expense of those that are not of the typical WASP voting bloc. The Christian doctrine of acceptance and tolerance appears long lost, and this same bigoted crowd often seems to be those that wonder why it is many people have turned to secularism.

Those wishing extreme "punishment" on those we incarcerate -- and are supposed to rehabilitate -- are wishing to play the role of the God of the Old Testament, not follow the teachings of their messiah.

micaksica··on Twitter Suspends 235,000 More Accounts Over Extremism
I am left with a great feeling of unease if not disgust at the Valley's long con on the concept of free expression. Social media likes to say it's the great equalizer, the democratic weapon. Twitter likes to pretend it's single handedly responsible for the Arab Spring, and with great irony they are now suppressing some of the results of that message that are no longer "on brand".

Social media isn't about, and has never been about, freedom of expression, as much as sometimes we seem to think it is. It's about saying whatever you need to to get scale, and then suppressing dissident communities that might cost you ad revenue or you personally find distasteful once you have the power and authority to do so. It's a cultural appropriation of a hacker ethos for the sake of a business purpose.

As for this action, very few things enrage me as much as Wahhabism and Islamic extremism; in fact, sometimes I struggle with the cognitive desire to write off Islam and the Muslim world as a whole because of ISIL and its followers.

However, I don't believe that this idea makes much sense. You cannot kill a meme by driving it off your platform; religious zealots have traditionally faced much worse persecution than being banned from a service. They will spring up again in places harder to detect, with tools that strengthen their communities. Their enclaves will no longer coexist alongside peaceful messages; they will be harbored entirely within their own safe spaces, echo chambers that strengthen their hatred in their isolation. Instead of a potential ISIL sympathizer seeing ISIL messages alongside trending topics against extremism and terrorism, they will spend time on extremist forums in which there is no dissenting opinion. They will not see pictures of people lamenting the death, they will have communities where this death is entirely praised. Instead of seeing football scores or other young people facing their same problems that may have differing religious opinions, they will find more people willing to indoctrinate them when exploring whether or not they find meaning in Islamic extremism.

Twitter may think they are taking the oxygen out of the atmosphere by banning them, but in reality they are simply shifting the fire to someplace where it can burn hotter.

micaksica··on Show HN: Simple express-like routing for front-end
I'm watching a movie so I haven't looked too deeply at this, but your regexes aren't safe from ReDoS according to substack's safe-regex [1]. It might be worth finding a non-regex-based way to parse regular expressions in case of some weird routes that could cause exponential-time parsing.

[1] https://github.com/substack/safe-regex

micaksica··on Nissan Motor Company has announced a new type of gasoline engine
> Possible issues with this design could be:

Let's also recognize that shortblock costs will be much, much higher with this design when you need a rebuild. Many engine builders won't touch this, and I'd suspect the Nissan OEMs will say that these engine shortblocks are "factory replaceable only". Who is going to make aftermarket bearings for the multilink setup? How does the engine operate under actuator failure?

micaksica··on Nissan Motor Company has announced a new type of gasoline engine
Don't advance ignition timing so far at 14:1 compression, and DI helps.
micaksica··on VeraCrypt to be audited
As a VeraCrypt user, I'm in support of this type of thing happening more for potentially critical open-source projects like this.

It'd be pretty cool if larger security consultancies with cryptographic expertise would band together and come up with a way to easily work with these types of projects, that way they could crowdfund exactly what they'd need to complete audits like this for themselves. I'd give a good chunk of change to projects that I used if they had a crowdfunding page for their cryptographic audit efforts that didn't expire ever.

micaksica··on The Election Won’t Be Rigged, But It Could Be Hacked
Of course it will be hacked. I find it hilarious that people think that our political parties have some type of moral code they actually use to play by the "rules", whatever nonexistent rules those are. As long as they aren't doing something directly illegal or can deflect the blame for illegal behavior to an underling that "misunderstood the directions", the incentive is there for ALL political parties to play as dirty as they possibly can. Democrat, Republican, whatever, doesn't matter.

The party's game is to win seats in Congress and the Presidency. Not win fairly. Not win "by the rules". To win, at whatever cost, as long as that cost isn't the elected positions themselves.

micaksica··on The Election Won’t Be Rigged, But It Could Be Hacked
I would suspect whomever voted for the winning "team" wouldn't care at all.
micaksica··on A New Wireless Hack Can Unlock 100M Volkswagens
> Why do so many people not care about security?

Security costs money.

micaksica··on The Tor Social Contract
> We will never implement front doors or back doors into our projects.

I hate the fact that this "front door" terminology is making it into the PR vernacular of a security product, especially in something as long-standing as this social contract is likely to be. By taking the line spoon fed by Tor Project adversaries, the project is validating the idea and putting it on equal cognitive footing.

micaksica··on Flash and Chrome
I agree that your number is better, and I was admittedly being lazy when filtering this data.
micaksica··on Flash and Chrome
> we've had better alternatives all along

We've had better alternatives on the desktop for over six years now, since Apple said "No Flash for iOS" in April 2010, when content creators panicked to capture that market and started conversion to HTML5 video. That already was a long time coming.

Chrome finally saying farewell to Flash in this manner forces the market to recognize that Flash is no longer an option even on the desktop.

As for my security argument: using the link above, if we start with vulnerabilities found in Flash Player after April 2010, that's still 830 of them.

micaksica··on Flash and Chrome
The end of an era, to which all I can say is good riddance. Flash Player has been responsible for 892 published CVEs [1]. The world is safer without it.

[1] https://www.cvedetails.com/vulnerability-list/vendor_id-53/p...

micaksica··on On Cybersecurity and Being Targeted
> It's odd not to examine the "contacted a friend at GitHub" part.

Authentication aside: what does somebody do to talk to GitHub if you don't have a friend at GitHub that's willing to chat with you? Would Kenneth have been given the Source IP address of the attacker if he didn't know someone there?

micaksica··on On Cybersecurity and Being Targeted
Good on Kenneth for being quick on the draw. I love 'requests'.

If you're a developer of a popular open-source project, this should serve as a warning to make sure you have multi-factor authentication on, yes, but it's even better to learn from this and come up with incident response plans with your core maintainer base. Ask among yourselves:

1. Do we have the ability to detect an overt breach like this one?

2. Do we have the ability to detect a covert breach (e.g. are our builds reproducible, auditable? Are our binaries signed? Do we know who our committers are?)

3. Do we have a consistent way to message users of the project of the compromise?

4. Do we have a way to deprecate/mark as tainted compromised versions of our module/package/application?

GitHub offers some technology to help in this regard. Sign your release tags, at a minimum [1]; sign your commits with developer keys if you're paranoid. [2]

As FOSS becomes more used in the enterprise, I suspect these attacks will become less of a rarity.

[1] https://news.ycombinator.com/item?id=11494997

[2] https://help.github.com/articles/signing-commits-using-gpg/

← PreviousPage 8 of 9Next →