HNHacker News
TopNewBestAskShowJobs

bunnie

2,002 karma · joined March 9, 2013

submissionscomments
bunnie··on On Contact Tracing and Hardware Tokens
Yes, that is the meaning. Person 1's individual time line looks like this to Person 1:

- Person 1 contracts the virus, becomes infectious, but shows no symptoms.

- Person 1 gives the virus to Person 4.

- Person 4 becomes ill and shows symptoms, thus seeking testing.

- A positive test result causes Person 4 to report the exposure. This causes their key to be flagged in the exposure database.

- Person 1 downloads the updated exposure database and then receives a notification that they were exposed due to a match to Person 4's key.

- The next step is up to Person 1. However, a perfectly reasonable scenario is Person 1 now thinks, "I feel fine, but I will be extra vigilant and in case I feel symptoms I'll go for testing right away!"

In this case, Person 1 would never register on the app as positive because as an asymptomatic carrier they would never suspect they have the virus, and thus never go for testing even though they are infectious.

bunnie··on On Contact Tracing and Hardware Tokens
Exposure Notification just lets you know you were exposed. No other details are revealed to anyone else, including health authorities, so it is entirely up to the judgment of the exposed if they should go for testing or to isolate. The presumption is if you feel fine you're likely to write the notification off as a false positive, or not be very proactive about seeking testing immediately (I'll go tomorrow after my important lunch meeting...I feel fine after all...)

Contact tracing, in this context, means your identity is revealed to a health authority that can require you to be tested and isolated, even if you happen to feel fine. This is an invasion of privacy but it also may be able to reduce the number or severity of super spreader incidents.

bunnie··on Aging Problems at 5nm and Below
Anyone else catch this gem:

But if you are creating a chip that other people will create software for...then you don’t really know.

This is in the context of assessing usage duty cycles of circuits for aging purposes.

I can imagine an era of exploits that rely on "aging out" paths that were assumed to be rarely used. Like rowhammer, but persistent -- fire up a process on a random cloud instance, run a tight loop of code to wear out an exploitable path in e.g. SGX, rinse lather repeat until you have the coverage you need...

bunnie··on Perovskite Neural Trees
Am I correct in understanding that this paper describes a 'neuromorphic device structure', measures a few instances of it, and then plugs a theoretical model of this structure into a simulation?

So figure 2A-F are measured on a single device, and figure 2G-I are just simulations based on a model derived from 2A-F and scaled up in silico to large networks?

In that case, nothing more than single devices were fabricated, but results reported as a hypothesized neural network... and also if I'm understanding this right, the device is basically a resistor whose resistance can be changed using a series of voltage pulses.

This leaves a lot of devilish system implementation details as an exercise to the reader; a system level comparison of this to existing ReRAM (resistive RAM) implementations of DNN accelerators would be enlightening.

bunnie··on MIT 6.004: Computation Structures
wow. setup and hold times have been demoted to 'demystification only' and not something that is part of the formal curriculum. when I helped teach this course in the 90's, it was a major section and if you could not answer basic questions about synchronous clock discipline, you could not get an A. It was as important as stack-based calling conventions.

I mean, I guess most 'computer science' folks today can have a fecund and profitable career and have never heard of these concepts, but... I hope some people still wonder, why do we have clock speeds, and what other alternatives might exist?

bunnie··on Open Hardware on Its Own Doesn’t Solve the Trust Problem
While power signatures are repeatable on a single-chip basis, from chip-to-chip the variation in individual transistor performance will require a tolerance to be applied on the threshold criteria for determining if a given power signature is correct or not across a population of chips. Furthermore, power consumption is also dependent upon temperature and voltage so that will need to be carefully controlled for the measurement. The wider the tolerance on the power measurement, the larger the implant that can be buried.

Unfortunately transistor performance can vary quite widely for a single design; recall that a single CPU mask design is often sold in several speed grades. These aren't different designs, they are all the exact same design but then tested to pass at a given frequency and power profile.

My intuition is that a simple implant would probably escape power characterization, and larger implants can be left off until a trigger condition is met. That condition could be made so that fuzzing is highly unlikely to hit it, e.g. a particular 64-bit number pattern has to appear in a given register to power on the implant.

The technique may be suitable to detect gross anomalous execution in a single well-characterized chip but I feel any robust criteria against false positives would also leave a sufficiently large margin for small implants to slip through undetected.

bunnie··on Visual6502 Remix
Doubtful - the 6502 had something like one poly and one metal routing layer. It was hand routed by a human; balancing the use of poly, metal and diffusion is pretty tricky and requires bending a few rules that would otherwise constrain an autorouter in order to get everything to fit.
bunnie··on Open Source Could Be a Casualty of the Trade War
The issue is not that it reduces interest in open source. In fact the article states there's evidence that open source solutions are getting renewed attention in the Chinese government.

The issue is that the executive order would make it unlawful to share technology with foreign adversaries. So it effectively forces open source projects to hard fork along geopolitical boundaries. For example, if (and these are still if's) Huawei were to be designated a foreign adversary; and, if Huawei were to develop a RISC-V implementation of interest; it would be unlawful for a US person to use that implementation, or otherwise "acquire" said technology from Huawei.

The underlying premise of the executive order, as I understand it, is that technology developed by, or under the influence of, foreign adversaries is potentially tainted. Thus to defend the US national security interest, US persons shall be penalized for using their technology.

Thus the concern is that US-based open source developers and users would be directly at risk by interacting with the very projects you cite, should they fall under the influence of a foreign adversary.

Or to put it more concretely: ARM might be very happy if Huawei were designated a foreign adversary, and Huawei invested heavily in RISC-V. Because then ARM could lobby US lawmakers to rule that RISC-V technology is tainted under the theories contained in the executive order, thus reducing competition from open source alternatives.

(editted to clean up grammar)

bunnie··on Spectre/Meltdown Pits Transparency Against Liability
After seeing comments around the Internet on the article, one thing I wanted to add is this:

The question is not whether Intel would accept a settlement of documentation instead of money, or whether Spectre/Meltdown are bugs or not.

The question is whether /you/ would offer an exchange of documentation for release of liability. Whether or not the maker accepts the offer is orthogonal to whether you are willing to take the first step in breaking the vicious cycles that keeps hardware closed.

If you're not willing to give any allowance for the fact that sharing documentation exposes makers to more liability, then stop demanding transparency. Nobody should be obligated to put themselves in harm's way solely for your benefit or as intellectual entertainment. Likewise, learn to live with proprietary drivers, undocumented bugs, backdoors, and potential exploits hidden in your hardware, because without a transparency compromise, none of these problems will have a sustainable solution.

bunnie··on I Broke My Phone’s Screen, and It Was Awesome
xobs and I have a game we like to play when we live in Shenzhen for extended periods -- it's called "let's buy a soldering iron at 2AM". We'll hack until some stupid late hour and then get hungry, and go out to find street food and "something else", e.g. soldering iron, spare parts, phones, power adapters, etc. in the street markets of Shenzhen. So far, we have not been disappointed. That city simply does not sleep.

This is in part because the EU and US is awake during Shenzhen's nighttime, and if people waited until the morning to fill all the orders coming their way, they'd have to spend all day catching up.

bunnie··on Releasing my book "Hacking the Xbox" as a free PDF in honor of Aaron Swartz
oops! good catch.
← PreviousPage 7 of 7