kijiki

14 ms·

121.
by kijiki 6y ago
Oh, I didn't realize they'd worked around MS removing LDT access. They did it by running in an 16bit x86 emulator, which is a pretty big hammer, but I guess win16 apps are old enough that the performance is still more than fine on
122.
by kijiki 6y ago
It was just a choice Microsoft made. Wine happily runs win16 apps on x86_64 Linux. There was a wine derived thing that used to work on Win64 to run win16 apps, but something in later windows versions broke that.
123.
by kijiki 6y ago
https://brad.livejournal.com/2116715.html some enterprise SCSI drives too. This was all back in the late 90's/early 2000's, no idea if it still happens with SATA or SAS drives...
124.
by kijiki 6y ago
I'd been hearing rumors (possibly spread by the mfgs to scare enterprises away from cheap IDE drives) about it during the late 90's and early 2000's. Then bfitz proved in in 2005, and it turns out SCSI drives sometimes do it
125.
by kijiki 6y ago
> ...a global constant would go in the TEXT section of the binary... Wouldn't it go into the .rodata section, not .text?
126.
by kijiki 6y ago
That isn't quite how it is implemented, there are no HSMs, we use SGX for that function instead. See my reply to Josh's follow up for details. You need a random id not the phone number, so other users can't do guesses unless
127.
by kijiki 6y ago
Yeah, there is a 32 byte random serviceid generated inside the enclave when it starts in "new" mode, so it is locked to the serviceid, not the HW, so we can migrate off failing/failed hardware. The only way to get a non-rando
128.
by kijiki 6y ago
The enclaves will flush the data (much like the hardware you mention in your first post) after some number of wrong PIN guesses. To do this securely made the whole thing quite difficult, because it means we can never persist anything outsid
129.
by kijiki 6y ago
Basically, SGX: https://github.com/signalapp/SecureValueRecovery The enclave is hardened against Spectre and LVI with this (BOLT/LLVM based), and other techniques: https://github.com/signalapp&#x2F
130.
by kijiki 6y ago
You can get 400Gbps bandwidth in commodity networking: https://www.fs.com/products/96982.html Not going to get that sort of latency without extreme custom chips though.
131.
by kijiki 6y ago
switchd living in userspace was in large part a result of the highly proprietary NDA's ASIC SDKs. Mellanox is making small (and welcome) steps in opening up by putting some functionality into their switchdev driver, but if you want a f
132.
by kijiki 6y ago
Cumulus co-founder and original switchd author here. Mellanox sells switches with Broadcom silicon, so certainly in the short and medium term there will be no changes there. Long term is harder to say. It is possible that once Mellanox&#x2F
133.
by kijiki 6y ago
The plan of record is yes.
134.
by kijiki 6y ago
> Hard drives that look like tapes. Tapes don't have fast (by spinning rust standards) random reads. Hinting in ext4 or NTFS is of course a waste of time, but CoW filesystems like ZFS or btrfs are in a much better position to handle
135.
by kijiki 6y ago
I am annoyed that they missed an opportunity here to fix SMR support in the non-GooFaceAmaSoft DC ecosystem. Announce a trade-in for anyone who has a Red and has a problem with device-managed SMR, with a CMR Red. Many, many people won&#x27
136.
by kijiki 7y ago
> N64 was pretty much an upgraded PS1 polygon engine (hardware was SGI dervied like the PS1) N64 was literally SGI derived, but PS1 was at best "SGI inspired". This comparison overstates the similarities. > After that Ninte
137.
by kijiki 7y ago
The PS2 was where this peaked. It has a weird multi CPU architecture with multiple CPUs and coprocessors, but was popular enough (dominant, really) that devs really invested in some cases. Shadow of the Colossus is a good example. They tr
138.
by kijiki 7y ago
The driver for recalls is demand from the largest customers. In Intel's case, mostly big cloud operators. They have a strong vested interest in pretending that sharing compute resources across customers is a safe thing to do, so they&
139.
by kijiki 7y ago
Signal already uses SGX for Contact Discovery, and has for many months. In all cases, Signal only uses SGX to improve cases where data previously was stored in plaintext. The idea is to change the required attack from "compromise sign
140.
by kijiki 7y ago
https://signal.org/blog/secure-value-recovery/
141.
by kijiki 7y ago
This might be fixable with the kernel's VRF functionality: https://www.kernel.org/doc/Documentation/networking/vrf.txt
142.
by kijiki 7y ago
So in this version of the story, the MCP defeats TRON.
143.
by kijiki 7y ago
Keypass is written in C#, so requires a .NET runtime. KeypassX is a rewrite in C++, using QT. KeypassXC is a fork of KeypassX, as KeypassX was felt to be unmaintained.
144.
by kijiki 7y ago
Yes, but those are fixed function designs like Trident or Tomahawk (yes, they name their switch chips after missiles). When Broadcom uses the term SOC, they mean "Switch on a Chip" to differentiate their single chip designs from o
145.
by kijiki 7y ago
It was never ARM. It used to be ARC, but these days it is x86.
146.
by kijiki 7y ago
MkLinux ran Linux as the sole server process on Mach on Macs. It was noticeably slower than the direct PowerPC port. It was done by Apple and OSF, and for a while was the only way to run Linux on NuBus Macs.
147.
by kijiki 7y ago
They still sold a 80487, of course. It was a '486 without the FPU being fused off, and when you plugged it into the "math co-processor" socket, it disabled the original CPU and took over both duties.
148.
by kijiki 7y ago
Bebop
149.
by kijiki 7y ago
It is also the only way for an xlib program to survive losing its connection to the X server. xlib will let you register a callback to handle loss of connection with XSetIOErrorHandler, but unconditionally calls exit() after your callback
150.
by kijiki 7y ago
Slirp is a little like NAT, but implemented differently. It creates what looks like a virtual NIC (literally in qemu's case, indirectly by SLIP in the original Slirp), and reassembles the packets it gets coming in from the guest OS or

More ›