6 ms·
Oh no! People expect us to do our jobs well and have absolute minimum legal standards and expectations of outcome? What a horror! What if we write code full of
by mrguyorama 4y ago
Oh no! People expect us to do our jobs well and have absolute minimum legal standards and expectations of outcome? What a horror! What if we write code full of bugs, fail to write good unit tests, fail to do any manual dev testing, fail to find those bugs in QA (because we fired all of them or don't let them have any power to stop broken stuff from being pushed out), fail to find those bugs in integration testing, fail to have robust systems that can tolerate that kind of bug, and then people actually hold us accountable for that POS?
Gosh, can you imagine if other industries had to deal with such oppressive requirements, like if the local taco truck had to abide by some minimum standards of food safety, or if engineers would be held accountable for a bad bridge, or if accountants were expected to actually do their job correctly?
What a terrible world that would be.
- s1k3s 4y agoYou didn't read the article, right? Go check it out, it brings up some good points. There's definitely stuff in that Act that's more than "absolute minimum legal standards", some even impossible to achieve.
- DyslexicAtheist 4y agocan you paste one that you feel goes beyond minimum or even "impossible"? otherwise this comment is just he said she said.
- s1k3s 4y agoYeah, literally the entire 2nd half of the article. Go read it, I'm not your tldr bot.
- DyslexicAtheist 4y agoI'm deeply familiar with the actual draft proposal of the law and no person working in security would consider these outrageous. this shit really is just best practice and good security hygiene. refusing to quote what you mean is bad faith. and you're not really contributing to the conversation
- s1k3s 4y agoSo you didn't read the article, you have no idea what you're talking about and you call me "being in bad faith". Is this Reddit now?
- kneebonian 4y ago> The CRA describes ’essential cybersecurity requirements’ which are well intended, and mostly ok, but leave a lot of room for interpretation. These requirements tell us to implement adequate denial of service & exploit mitigation techniques, for example, and no one can be certain what that means Service exploit mitigation techniques? Really why didn't I just think about not writing bugs, and vulnerable code.
- DyslexicAtheist 4y agoa shame that he is unfamiliar with RED. It's meaning is literally just system hardening as it is also defined in RED (CRA is just an expansion of RED to the rest of the ecosystem), which is in this contexts outgoing firewalls rules on devices, system hardening, anomaly detection, ... It is not a definitiv list of things because this would change based on what makes sense on a system. Instead you need to demonstrate that you've considered a threat model when applying the mitigation. And the mitigation is sufficient for the intended purpose. One example could be limit what the system can and can't do. And don't allow it to communicate with the whole world when your only required endpoints are api.samsung.com, an ntp server, DNS and MQTT. A shame that he had to write this hit-piece when he could have asked what notified bodies are testing _today_ to meetx requirements for RED.
- kristiandupont 4y agoHere's one part: >(f) protect the availability of essential functions, including the resilience against and mitigation of denial of service attacks; >Did the EU just require me to make software that can withstand (unspecified) denial of service attacks? Something that is mathematically proven impossible? That does not seem like the intent of the paragraph. My first thought is that it's a poorly worded (though legalese oftentimes needs to be) way of saying that devices should not easily be turned into DDOS nodes. But it might also just say that even if it's under DDOS attack, there should be a way to operate essential functions still, which is very much possible with some compartmentalization.
- mkmk3 4y agoWould be nice, but I think since (a-e) weren't in that line and that (g) is directly addressing that, that would be incredibly bad wording. Regardless, I can imagine there are some products with 'essential functions' which require the channel that could be DDOSd, no? My stance here is that it's very broad, and I think it's easy to create an exploitable system from these directives. But unfortunately the problem is real and the mitigations complex. I was buying into this initially because of that, it seems reasonable without much thought on what the exact solutions look like, which I think makes it more dangerous. If other engineering fields have seen this process, and the involved regulatory bodies have stayed independent of large corporate interests, I guess we should have a good shot. But with my lack of knowledge on that topic, I hold some trepidation for the future of smaller software shops and individual developers. > (g) minimise their own negative impact on the availability of services provided by other devices or networks;
- krono 4y agoOf course, as per usual, this will come with entirely unfair and unproductive enforcement. Multinational corporate violators will be left alone or get sent on their way with a slap on their wrists, and small one-time hobbyist violators will get prosecuted into dissolution.
- ohgodplsno 4y agoSource: I made it up This is not what has happened with previous regulations. In fact, it's mostly weaponized against US companies, but that's mostly because it's fun and deserved.
- krono 4y agoSource I have experienced this with my own business, and saw it happen to other commercial as well as non-commercial entities with previously implemented acts and directives. It's not dissimilar to how the tax authorities always seem to pick small timers for a random extensive audit.
- DyslexicAtheist 4y agothere is nothing in history that could be used as a precedent to predict how this will be enforced. big companies will be in the news very hard for violating these laws. no-name small timers might get a slap on the wrist. but pretty sure fines will be proportional. about time companies are held accountable
- krono 4y agoAs previously implied this does not conform to my own observations The idea is good and I'm all for it, but mostly due to said observations I'm not convinced its practical implementation will be very effective at all
- ikiris 4y agoWon't someone think of the poor oppressed small business owners. It's not like they're the cause of half of regulations or anything due to all the scummy small business owners...
- ohgodplsno 4y ago[flagged]
- tgv 4y agoThe negative comments are indeed a bit hypocritical. It's as if the profession that ships faulty products almost by definition throws a fit because a (legal) product might not be perfect on the first attempt.
- yazzku 4y agoWhy is this downvoted? Did it hurt someone's ego?
- mrguyorama 4y agoA lot of people's paycheck on this forum depends on having zero standards of quality in the entire industry.
- brushfoot 4y agoIt violates HN guidelines [0]: > Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith. > Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. > When disagreeing, please reply to the argument instead of calling names. It's okay to disagree with someone, but saying their comments are hypocritical and that they're throwing a fit is not okay. 0: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- yazzku 4y agoThat's all fantastic, but this guy actually has a point. Software quality at large is pathetic, anybody who uses technology knows this, and especially those who develop it for a living. The lack of regulation plays a big role in this. The field can barely call itself engineering. Yet the guy's comment also just happens to make the fanboys uncomfortable, so he gets immediately down-voted (didn't even last two minutes). On the other hand, look at that motherfucker up there who dismissed my comment saying that all I do is type too fast. Now that is clearly against the guidelines, yet no down-votes? Fascists, too, are very good at applying double standards.
- yazzku 4y agoUnimaginable horror can come from stopping the endless pursuit of profit and the cutting of costs at the expense of quality in engineering. And to hold companies accountable? That is just over the top. Can you imagine if, next, people had... the right to repair? Or the right to look at source code? Terrible consequences.
- Longlius 4y agoThis article points out that this doesn't just apply to companies. If you maintain an open-source project and accept donations, then you're potentially affected as well.
- fabianhjr 4y agoAdoption of open source, most open source licenses already come with broad waivers so compliance would fall mostly on the adopters.
- ahubert 4y agothat's not how the act works, sorry.
- fabianhjr 4y agoArticle 6, Numeral 2 "In determining the level of cybersecurity risk, one or several of the following criteria shall be taken into account" seems very reasonable in scope and wouldn't include most open source/free software.
- deleted 4y ago[deleted]
- brnt 4y agoThis. It's about time software is treated like any other engineering: lives depend on it. Not enough heads are rolling.
- BeFlatXIII 4y agoAll software or just important software?
- Jensson 4y agoAll software storing user details that would be a problem if they were leaked, I'd assume. That would include basically all software with a login.
- brnt 4y agoUntil proven irrelevant I'd say.
- BeFlatXIII 4y agoProven irrelevant by actual de facto use or by the license? In other words, would adding "this software is not certified or fit for medical, aviation, nuclear, etc…" suffice to exempt it (assuming it is not then sold to medical or airplane manufacturers)?
- kitsunesoba 4y agoThe real question is if execs and management are going to allocate the extra time and resources required to make consistently meeting these standards reasonably achievable or if they're just going to squeeze harder and expect more without any adjustments. I would bet that a lot of devs actually want to write high quality, well-tested code and engage in proper project hygiene but simply aren't given the bandwidth required to do so. In my experience everything is so tilted towards "ship now, fix later (maybe)" that any IC's efforts to do things more correctly is a bit like trying to swim upstream.
- Atlas22 4y agoIll place my bet that the squeeze will get harder on developers and there will be new "compliance officers" in the office that dont actually do anything but make silly demands to waste peoples time. So pretty much the same as every other security regulation...
- fwlr 4y agoCan you imagine if taco trucks gave away food for free, or if engineers built and maintained some of the biggest bridges in the world out of their own pockets and didn’t ask for a dime, or if accountants did their job without charging any fees?
- steve76 4y ago[dead]
- Luker88 4y agoYou might have missed the part where this is already scaring Theo de Raadt, to the point of recommending EU users not use openSSH anymore. How many here are confident of writing software as securely as Theo? edit: I still think this is going in a good direction, but at this stage this kills a lot of small businesses, startups and open source. Requiring certification for every release means killing off most software, let alone the fees. Forget multiple supported releases or LTS, everything will be rolling release.
- bennysonething 4y agoAnd who gets to say what these good practices are? Until recently everyone thought Clean Code was a wonderful book full of great coding advice, now we see that it's full of really crap examples. Does all public code on GitHub need to be audited?