Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dwattttt
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
151.
▲
by
dwattttt
5mo ago
Yes, it is helpful for a company to be very clear that in a choice between the safety and integrity of their customers, and profit, they are choosing profit.
152.
▲
by
dwattttt
5mo ago
There is quite a bit of irony, or depending on your perspective it's the whole point, that this response is a great example of 'glorified autocomplete'.
153.
▲
by
dwattttt
5mo ago
I've brought this up with leap second adjustments; a process you do once every two years is one you'll never get good at. If you want them to go smoothly, do them monthly. LetsEncrypt has been a great example of this in certificat
154.
▲
by
dwattttt
5mo ago
> Why are you not using this through KiCad? That's what I would expect an amateur to do; especially since they handle the UX that you are complaining about. They sound like an amateur at circuit design, not software engineering (whi
155.
▲
by
dwattttt
5mo ago
Your question was "how many high profile privilege escalations Windows has had recently" then? I can't think of any, 0?
156.
▲
by
dwattttt
5mo ago
If you think Linux is on their first or second, I'm not sure how or what you're counting.
157.
▲
by
dwattttt
5mo ago
> The alternative they present is arguably less secure because the function pointer will remain writable for the life of the process They also suggest an alternative to storing the function pointer, store the bit flags that decide which
158.
▲
by
dwattttt
5mo ago
#1 NSA, I get it now!
159.
▲
by
dwattttt
5mo ago
> To spawn a future on tokio, it has to implement `Send`, because tokio is a work-stealing executor. Tokio's default executor is a work-stealing multi-threaded executor, but it also has a local executor and a current-thread executor
160.
▲
by
dwattttt
5mo ago
I'm no expert, but the kernel is shared between all containers and the host. I don't believe the kernel maintains separate page caches for each container; a malicious CI job could corrupt a binary from any container, or the host.
161.
▲
by
dwattttt
5mo ago
Defence in depth matters, but an analysis here shows that the same mechanism used to breach the outer layers (getting administrative access) can be used to breach the next layer (more thoroughly prodding Edge or Chrome to give up passwords)
162.
▲
by
dwattttt
6mo ago
Yes, I believe it's possible to buy an Apple TV without owning an iPhone.
163.
▲
by
dwattttt
6mo ago
They could control their own Apple TVs to allow that dialogue to be dismissed via the TV controls.
164.
▲
by
dwattttt
6mo ago
I've seen C written by people who learned it "exactly once", in let's say the 2000s. They're the same people who insist that all the safety & linting introduce since was pointless. I'll take C written by pe
165.
▲
by
dwattttt
6mo ago
> Because even if the newer shinier compiler/toolchain had the issue fixed, most companies wouldn't upgrade to it at that point. It's almost never desirable to change your toolchain for a shipping product, you're just
166.
▲
by
dwattttt
6mo ago
To elaborate on "prevent new dependencies", dependency resolution will never choose a yanked version. However the yanked version remains hosted.
167.
▲
by
dwattttt
6mo ago
> a gif is not a video. They're not that different; the image codec WebP is derived from VP8's intra-frame coding.
168.
▲
by
dwattttt
6mo ago
It sounds like your second statement contradicts your first. But also, WUFFS exists and it looks like the Google Chrome GIF decoder ships in it: https://github.com/google/wuffs
169.
▲
by
dwattttt
6mo ago
This thread talks about driverless cars; vehicular manslaughter requires negligence or intent, do you want to find narrowed statistics for driverless cars that are restricted to negligence or intent?
170.
▲
by
dwattttt
6mo ago
> Linux has earned a stunning amount of respect and gratitude by actually providing stunning utility and quality. IE, it's not just a random object like a cow that everyone decided to worship for no reason. I agree. > A sacred co
171.
▲
by
dwattttt
6mo ago
> a company, after commissioning a security review, needs to hire a different firm to handle the vendor interactions These vendor interactions you're referring to are the company's customers, correct? Are you proposing the comp
172.
▲
by
dwattttt
6mo ago
Guess the other supported kernels aren't supported enough
173.
▲
by
dwattttt
6mo ago
Yes, this is the sacred cow status being referred to.
174.
▲
by
dwattttt
6mo ago
> I struggle to find anything on this post that wouldn't be caught by some kind of unit test or manual review, especially when comparing with the GNU source for the coreutils. > If you do a rewrite, you should fully understand an
175.
▲
by
dwattttt
6mo ago
I do wonder whether people got down the article enough to see the list of bugs patched in GNU coreutils. That "perfectly good code" that it sounds like no one should question included "split --line-bytes has a user controlled
176.
▲
by
dwattttt
6mo ago
A question: why is git involved at all in this? You don't want a repository.
177.
▲
by
dwattttt
6mo ago
I do agree with this, but just to be clear (for others), you don't need any runtime managing resource lifecycles to know that there shouldn't be pointers into free memory, such as the currently unused portion of the stack.
178.
▲
by
dwattttt
6mo ago
In the general case it's absolutely not worth it. In the context of "you want a large number of OS threads, and are willing to go to some effort", it's theoretically something you'd want to do; suppose the startup f
179.
▲
by
dwattttt
6mo ago
Specifically this lint: https://rust-lang.github.io/rust-clippy/master/index.html#la...
180.
▲
by
dwattttt
6mo ago
> C programs can't do it because pointers to stack allocated objects may exist. They sure shouldn't exist to the unused region of the stack though; if they do, that's a bug (because anything could claim that memory now). Y
More ›