alt Hacker NewsThe Duty of a Scholar
Comments
Wow that showed up quickly.
Readers might also consider my 2020 post "On the use of a life" to be an interesting companion piece: https://www.daemonology.net/blog/2020-09-20-On-the-use-of-a-...
> Members of the IEEE commit, for example, "to hold paramount the safety, health, and welfare of the public..." without that duty being limited to hazards arising from projects employing the Engineer in question: The duty "to disclose promptly" vests in any Engineer who recognizes that the hazard exists.
As an active member of the IEEE for over a decade now, I have never seen anyone (aside from the author here) take this duty seriously. There are plenty of IEEE members working on things that directly cause such hazards.
The Intel claim it wasn't a problem: [1]
Today, it would be a bigger deal. In the age of AI, exploiting hard to exploit holes is so much easier. AI has patience limited only by your budget.
[1] https://www.itnews.com.au/news/intel-soothes-hyperthreading-...
He sounds somewhat like R. K. Merton, and thus it was a good read.
> While I had some bills to cover — being a type 1 diabetic, I had to purchase insulin — living in Canada meant that I didn't need to worry about the risk of extraordinary costs from a hospital stay. Had I been living in the USA, I would have needed to prioritize seeking employment and medical insurance and likely would not have been able to discharge the duty which fate had thrust upon me.
God bless Canada.
[flagged]
I'm not sure modern academia has very much left to do with scholarship in the sense quoted in this article.
This is unfortunate.
Intel's response was:
> Timing exploits has been known to the security community since the mid-nineties. From a real world standpoint the attack is not practical.
And this is basically the state of the art today, even with Spectre. You can demonstrate the vulnerability under controlled conditions but having those conditions arise in production is not practical in the engineering sense.