Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
__michaelg
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
__michaelg
7y ago
No mention of runtypes which looks pretty similar? https://github.com/pelotom/runtypes
32.
▲
by
__michaelg
7y ago
Normal :) Same for the Boeing 787 back in 2015: https://news.ycombinator.com/item?id=17907654
33.
▲
by
__michaelg
8y ago
ZFS, Btrfs, etc. essentially provide that with filesystem snapshots; LVM snapshots probably also works for that. Not sure whether any easy tooling around it exists though.
34.
▲
Goodbye, EdgeHTML
(blog.mozilla.org)
1178 points
by
__michaelg
8y ago
|
657 comments
35.
▲
by
__michaelg
8y ago
I read 'Modem' instead of 'Modern' and it still made sense.
36.
▲
by
__michaelg
9y ago
BeagleBones are awesome for these kinds of things. They are very similar to RPis but in addition to the ARM core they have two embedded hard real-time capable CPUs (dubbed PRUs) that run at 200 MHz.
37.
▲
by
__michaelg
9y ago
Networking library in C? Nice. Who is afl'ing it first?
38.
▲
by
__michaelg
9y ago
Other fun colors are https://en.wikipedia.org/wiki/Selective_yellow and https://en.wikipedia.org/wiki/Baker-Miller_Pink
39.
▲
by
__michaelg
9y ago
This is fun in theory, but doesn't really give you a lot in practice. A few random points: * On many server systems swap is already disabled today (for availability reasons), so you don't really win anything. (Although what you&#x
40.
▲
by
__michaelg
10y ago
Nice project! Unfortunately, as with most interpreters written in C, afl finds segfaulting bugs in a few seconds. In your case at least empty variable substitutions are broken. E.g., entering $ foo will crash.
41.
▲
by
__michaelg
10y ago
It looks like Kelsey didn't write a lot of assembly before. There are quite a few things you either wouldn't do -- like `cld` for no reason -- or most people (and compilers) would do otherwise -- e.g., `xor ebx, ebx` instead of `m
42.
▲
by
__michaelg
10y ago
Lesson learned: blacklists are catastrophic for security purposes, because you will always miss something. Even if you didn't miss anything, the next kernel release will just add something new that I can exploit.
43.
▲
by
__michaelg
10y ago
$ cat > nope.c <<EOF > #include <stdio.h> > void main() { > write(creat("nope.nope"), "oh no\n", 6); > } > EOF $ make nope $ ./fssb -- ./nope fssb: ch
44.
▲
by
__michaelg
10y ago
Looks like a scan of a German book or paper. Any idea which one?
45.
▲
by
__michaelg
10y ago
Sure, but it's not any better than the Android FDE, and thus kind of defeating the point of the article. If everyone just uses the default setting, then iOS's encryption is theoretically and architecturally better, but it won'
46.
▲
by
__michaelg
10y ago
Given that app developers need to actively use those iOS features, the obvious question is: How much of my app data is actually encrypted that way? It's much harder to get these things right (e.g. you want your fancy sync and notificat
47.
▲
by
__michaelg
10y ago
Doesn't work on Ubuntu 12.04's Chromium. (Chromium 37.0.2062.120 (Developer Build 281580) Ubuntu 12.04)
48.
▲
by
__michaelg
10y ago
> I don't know anything about Peugeot. Probably hybrids so who cares. YTD in Germany, Renault sold twice as many purely electric cars (1836 Zoes) as Tesla (978 Model S and 56 Model X.) Source: https://www.goingelectric.de
49.
▲
by
__michaelg
10y ago
$ stat "$(which stat)" shellcheck or its online version http://www.shellcheck.net/ help a lot
50.
▲
by
__michaelg
10y ago
LargeCorp foo division buys BigCorp's foo division in order to disrupt the foo business? That seems... unlikely.
51.
▲
by
__michaelg
10y ago
Isn't the real question whether we need to update Unicode now?
52.
▲
by
__michaelg
11y ago
Whenever I mention that I don't use compilers I tend to get strange looks from people who cannot imagine writing assembly with using a C or Fortran compiler. And so I have to defend my choice and explain why, over and over. Some people
53.
▲
by
__michaelg
11y ago
This article a bit fishy to me. E.g.: > In almost all network stacks, per-flow IPsec processing is serialized due to implementation specific constraints of upper level protocols that require in-order packet processing and lower level har
54.
▲
by
__michaelg
11y ago
Yes. As one of my professors used to say: Using "quite obviously" in non-fiction is quite obviously wrong in most cases.
55.
▲
by
__michaelg
11y ago
This actually exists in some countries. E.g. in Europe there are (were?) several companies selling modem/ISDN+satellite bundles. All the upstream and parts of the downstream would travel through land-line while larger downloads would b
56.
▲
by
__michaelg
11y ago
Agreed. This shouldn't be an issue for anyone using cloud services -- or any computer really. Except for some super duper redundant mainframes maybe, you should always be able to deal with losing a component not matter what it is. If y
57.
▲
by
__michaelg
11y ago
Huh? $ curl -i codes.io/600 HTTP/1.1 -424 ??? ...
58.
▲
by
__michaelg
11y ago
The cool thing about the address calculation is that there is a LEA instruction (load effective address), which gives you the resulting address. I.e. instead of actually loading the value from the calculated address in memory, it gives you
59.
▲
by
__michaelg
11y ago
canada-eh-1
60.
▲
by
__michaelg
11y ago
I would argue that copying more bytes (as demonstrated) is correct behaviour: (1.) The function is supposed to append a string to another, not paste a byte range into another one, leaving extra bytes at the end untouched. Thus the functio
More ›