codys

14 ms·

361.
by codys 11y ago
> Assuming this updates the loader It doesn't. The model I presented presumes that it is unchangeable. > anyone with physical access for five minutes can permanently brick the phone, without opening it Pick one: - you can always
362.
by codys 11y ago
I believe the parent comment was referring to "allowing updates of the OS without requiring either unlock of the device or a wipe of stored data" as the backdoor.
363.
by codys 11y ago
This really isn't difficult to do: - loader A stores a (PubKey,NextLoader) and has the ability to blank (via actual blanking or deletion of an encryption key) the entire device. - loader A provides a new-key(PubKey,NextLoader) method w
364.
by codys 11y ago
I'm not distributed systems expert, but I don't see any attempt at responding to: > 1. Distributed locks with an auto-release feature (the mutually exclusive lock property is only valid for a fixed amount of time after the lock
365.
by codys 11y ago
For many projects (that aren't depended on by other projects), adding versions in Cargo.toml is just more work without payoff. Specifically, if one is already shipping Cargo.lock (in a way that it is used), `cargo update --precise` (in
366.
by codys 11y ago
> Instagram a non-exclusive, fully paid and royalty-free, transferable, sub-licensable, worldwide license to use the Content Does "sub-licensable" not allow the "partners" you speak of?
367.
by codys 11y ago
It always feels funny to me to refer to the ISM bands (the spectrum itself) as "unlicensed". - Devices operating there have to be approved - There are rules about how the devices work - There are rules about how the _operator_ is
368.
by codys 11y ago
Not in sales, but: Author expects interviewees to "tell you what you want to hear", recommends requiring their W-2, admits that companies oversell themselves too, but doesn't appear to offer the interviewees the same insight
369.
by codys 11y ago
why?
370.
by codys 11y ago
I suppose I just disagree with the sentiment that "something is pretty bad already, so we should allow regulation to make it worse". I don't think that is a good idea. Right now, not all control is given to the WiFi firmware
371.
by codys 11y ago
Immediately assuming we must give something up is a poor way to proceed. If we had made that assumption in the past, the clipper chip[1] would have been a "success". After all, the NSA doesn't care about software freedom eith
372.
by codys 11y ago
It'd only be problematic legally to ship GPLv3 (or similar) licensed software. v3 adds language mandating that the software be replaceable.
373.
by codys 11y ago
Ah yes, lets add all the problems of vulnerable basebands to wifi routers too. No issues there. Edit: And the possibility for purposeful maliciousness on the part of the baseband manuf. And after all, all a closed system like a baseband do
374.
by codys 11y ago
I clicked expecting an actual discussion of "algorithm fairness" in the sense of how a scheduler can be fair (what that means seems to elude me still). Instead of talking about "algorithm fairness", it appears to be talk
375.
by codys 11y ago
> Has anyone actually confirmed that Chrome is continuously sending audio back to Google? That's not relevant. The problem is that they _could_ do that (for some subset of users, potentially) and in most cases no one would even not
376.
by codys 11y ago
I missed that the parent comment added that conditional. I suppose I should have responded directly to them instead of under this comment then.
377.
by codys 11y ago
Arbitrary code controlled by a single organization (Google) is still arbitrary code.
378.
by codys 11y ago
In case anyone is wondering, "Maxwell" is Nvidia's current shipping GPU microarchitecture: https://en.wikipedia.org/wiki/Maxwell_%28microarchitecture%2...
379.
by codys 11y ago
I hope so, but no one except systemd is using it yet. Last time I checked the sd-bus.h header isn't installed with systemd yet due to the systemd folks concern that that API for sd-bus wasn't finalized yet. It would be very intere
380.
by codys 11y ago
The article lists percentages of capacity as if every battery (or battery controller) reports the full range of capacity (or allows charging to actual full capacity or discharging to completely empty). I had thought that many manufacturers
381.
by codys 12y ago
> At this point they will release the busybox sources, potentially including the in-house version, but not under GPL Do you mean they'll release the busybox sources potentially not under GPL, or the in-house version potentially not
382.
by codys 12y ago
There's a governance structure? That's news to me. I was under the impression that a few primary contributors (mostly/all mozilla employees?) are gatekeepers to merging anything. Having an "RFC" issue tracker isn&#x
383.
by codys 12y ago
Yes, even c99 has them IIRC. The issue that was called out, however, was the use of "FOO(x, ## __VA_ARGS__)". GNU C has an extension that causes the ',' to be removed if __VA_ARGS__ is empty. AFAIK, it is not standard.
384.
by codys 12y ago
While it is unfortunate they don't use forward-declared structs instead of void pointers, that only means that potential type checking that could otherwise be done by the compiler does not happen, the use of void pointers in and of its
385.
by codys 12y ago
The article is comparing intrusive (see linux's list_head as an example) vs non-intrusive (std::list) lists. Given that comparison, intrusive lists (which the article appears to argue for over std::list) are almost certainly better (ba
386.
by codys 12y ago
Yep, I remember that and http://boxcar2d.com/ ending up on HN some time ago
387.
by codys 12y ago
The page says "bonus points are given for each proper step forward". So it appears they are optimizing for whatever their idea of a "proper step" is.
388.
by codys 12y ago
A more accurate title for the slide deck might have been "Getting started _modifying_ Rust". Only a single slide deals with "contributing" the changes made. And I'm happier with the actual slides than the ones the t
389.
by codys 12y ago
Anyone know what the things he "couldn't talk about" were? I was hoping to hear the open mic bit at the end for a hint but the video is cut off.
390.
by codys 12y ago
I'm interested in knowing if this affects Windows XP. From the page: > Other versions or editions are either past their support life cycle or are not affected And XP is unlisted. Seems to imply that it could be either one.

More ›