Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
quotemstr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
91.
▲
by
quotemstr
2mo ago
Implementation language is incidental. Rust is... fine, I guess? But I wouldn't mandate modules use it. What's important is to move PAM out of process and sandbox the process host (using landlock, namespaces like bwrap, whatev
92.
▲
by
quotemstr
2mo ago
Everyone doing parallel biometric and password authentication on Linux today is either running two PAM stacks in parallel (which is meta-policy that kind of defeats the purpose of PAM) or just bypassing PAM entirely.
93.
▲
by
quotemstr
2mo ago
PAM really needs to be ravamped and support for (among other things) running multiple stacks in par@llel added. This way you could ask for a password OR a fingerprint
94.
▲
by
quotemstr
3mo ago
It'd look like Graal, which is a real thing you can use today.
95.
▲
by
quotemstr
3mo ago
Classic ciphers are damn fast and small compared to PQC. If you're doing PQC anyway , doing classical cryptography at the same time has negligible cost. That makes attempts to push PQC-only modes super suspicious to me. Smells like Du
96.
▲
by
quotemstr
3mo ago
One attack weakens HAWK, a post-quantum cryptography cipher candidate. I don't trust these PQC things one bit. I'll use them in combination with a strong clasically-resistant cipher (in so-called hybrid encryption modes), but not
97.
▲
by
quotemstr
3mo ago
How do their servers know I'm running a proxy, exactly?
98.
▲
by
quotemstr
3mo ago
If I own a computer, I should be able to run whatever damn software I want on it, including software that provides a network proxy to others. (N.B. a smart TV is a computer I own.) Yes, yes, we should fight deceptive software that doesn
99.
▲
by
quotemstr
3mo ago
> And I also think it is totally fine to use Rust even if you could use a GC language like Go or Fil-C. The problem with choosing Rust over a GC language like the above (or a good one, like OCaml) isn't that it's not "fine
100.
▲
by
quotemstr
3mo ago
Your argument is literally that there is too much unsafe code.
101.
▲
by
quotemstr
3mo ago
That's a lot of words to say that the problem with Rust is that people you don't like are allowed to write unsafe code.
102.
▲
by
quotemstr
3mo ago
> It is not in scope of memory safety to make sure that logic not related to memory accesses works as you expected This logic is related to memory accesses. This is not an issue that can occur in systems that provide the memory-safety
103.
▲
by
quotemstr
3mo ago
> Also, Fil-C’s guarantee that it will panic on OOB or if a race goes badly Fil-C as currently implemented does not guarantee panics on unsafe accesses due to races. You dodge the problem by using a private definition of safety under dat
104.
▲
by
quotemstr
3mo ago
> In a race, you at worst access an object you could have loaded from whatever field you were racing on. Suppose a pointer ptr is initialized to foo and transitions once to bar; suppose also that x is attacker-controlled. Then, T1: T
105.
▲
by
quotemstr
3mo ago
Races in Fil-C allow access to one object through a pointer to a different object if there's an attacker-controlled offset involved. Fil-C's safety guarantees therefore fail to apply in this situation.
106.
▲
by
quotemstr
3mo ago
If we strip away the semantic maneuvering, your argument becomes this: Rust is unsafe because it lets people who aren't you, Pizlo, write unsafe code. Safety means trusting only you with machine code. Anyone could do the same with a Ru
107.
▲
by
quotemstr
3mo ago
Any safe system has unsafe parts. Quibbling about whether these parts are called "blocks" isn't useful. The term changes nothing.
108.
▲
by
quotemstr
3mo ago
Every one of these posts is the same. There's this weird blindness to the problems and imperfections in Fil-C --- just shouting down. It reduces my confidence in Fil-C as a whole. Rust, for all its faults, at least engages with its cri
109.
▲
by
quotemstr
3mo ago
Okay, let me know when I can call process_vm_writev or ptrace and have Fil-C verify safety properties on the result.
110.
▲
by
quotemstr
3mo ago
> is going to be short lived because someone will train an AI on a corpus of human keystrokes and get a replication You can remotely attest the input devices. You can do it anonymously (long story, but doable) and without requiring some
111.
▲
by
quotemstr
3mo ago
Both Rust and Fil-C have unsafe blocks, but in Fil-C latter system, only Pizlo gets to write them. Why am I not filled with confidence?
112.
▲
by
quotemstr
3mo ago
The article is clear that LG is talking about banning all proxies, even voluntarily installed ones. A smart TV is a computer. Why should the owner of a computer not be allowed to run any program he wants?
113.
▲
by
quotemstr
3mo ago
It is, though. Why should I not be able to agree, with sufficiently informed consent, to route traffic through a connection I operate via a computer I own using software I've chosen of my own free will to install? What's the diffe
114.
▲
by
quotemstr
3mo ago
Is the mask ROM really going to be worth it over Carmack's high-bandwidth-flash concept? I mean, sure, I could be convinced I guess, but it's not obvious.
115.
▲
by
quotemstr
3mo ago
I love GNU Parallel too. I love how it's free software and how I can patch out the obnoxious citation notice.
116.
▲
by
quotemstr
3mo ago
Interesting. Is the speedup from specializing for the shape of Llama 3.1 or are they (contra my mental model) actually winning on burning in the weights?
117.
▲
by
quotemstr
3mo ago
You can pipeline in software too, and even with a dedicated circuit, you need to put weights somewhere , because you're not going to have a special partially-applied FP8 FMA unit for each of your trillion model weights. I can accept t
118.
▲
by
quotemstr
3mo ago
Ah, right. I misremembered. Does Taalas have a meaningful advantage here then?
119.
▲
by
quotemstr
3mo ago
> Cerebrus/Talas They are fast, but they're still programmable accelerators, not a model burned into the gates.
120.
▲
by
quotemstr
3mo ago
What precisely is an ASIC supposed to do that a more programmable accelerator can't? Memory latency is memory latency: doesn't matter whether it's embedded in a cache-line wait state or some flipflop state machine. ROM isn&#x
More ›