Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phkamp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
121.
▲
by
phkamp
5y ago
:-) Feel free to ask any questions...
122.
▲
by
phkamp
6y ago
Underestimating what an organization like NSA has the resources and imagination to do, is a chronic ailment. https://archive.fosdem.org/2014/schedule/event/nsa_operation...
123.
▲
by
phkamp
6y ago
"in case someone reading will actually at some point need to prepare for such threat" You mean like any human rights organizations who send people to authoritarian states ? You mean like any Foreign Ministry sending a courier out
124.
▲
by
phkamp
6y ago
Wiping disks has not been possible and has not been trusted since embedded controllers on the disk-drives took over bad-block remapping in the late 1980-ies. It's even worse with SSD drives, where the "hidden reserve" many ti
125.
▲
by
phkamp
6y ago
This scenario suffers from what I call "IT-Dude-Syndrome". IT-Dude-Syndrome is when IT-people come up with scenarios which hinge on "IT-Dude" being smarter than everybody else in the whole world. First, if you're su
126.
▲
by
phkamp
6y ago
There are no "positive" outcomes in that sort of situation. Being able to prove that you cannot possibly decrypt the partition, moves you out of the XKCD 538 scenario. That is a "much less negative" outcome.
127.
▲
by
phkamp
6y ago
"Denial of encryption" is no different from "Denial of having password", and leads you straight into XKCD 538. If the adversary does not belive you, their best bet is to keep torturing you, until they get their way. What
128.
▲
by
phkamp
6y ago
No ? The only problem OP has solved is detecting overwriting of metadata inadvisably comingled with the user data. That problem does simply not exist in phkmalloc, or jemalloc for that matter, writing past the end or before the beginning of
129.
▲
by
phkamp
6y ago
The particular problem they boast about having solved,does simply not exist in the malloc(3) I wrote 23 years ago, because it does not have the silly linked list to begin with. In addition to all the security problems inherent in mingling m
130.
▲
by
phkamp
6y ago
FreeBSD solved that problem 22 years ago: https://papers.freebsd.org/1998/phk-malloc/ (And got better malloc(3) performance at the same time.)
131.
▲
by
phkamp
7y ago
My first thought was "XKCD 463"
132.
▲
by
phkamp
7y ago
The Lost Generation discovers IBM Mainframe Channel Programs? Want to bet if they are going to make all the same mistakes themselves, or if they are willing to learn from history?
133.
▲
by
phkamp
7y ago
Some of the first experiments with coaxial lines were indeed made by pulling a center-conductor into standard copper pipes. There are several articles about that in BSTJ, with pictures.
134.
▲
by
phkamp
7y ago
The choice of 75 Ohm is documented in ultimate detail in Bell Systems Technical Journal. Here is a 1934 article as an example, long before anybody had even named microwaves: https://archive.org/details/bstj13-4-532 75O
135.
▲
by
phkamp
7y ago
Sounds familiar... Ohh, right: https://queue.acm.org/detail.cfm?id=2508864
136.
▲
by
phkamp
7y ago
You have no idea how much money businesses have lost in the long run, because they said that about IBM mainframes. Keep your options open by keeping your code portable.
137.
▲
by
phkamp
7y ago
My most constructive advice is that CS education should "go concrete" often enough to de-mythologize the predictive powers of big-O notation, and have the course contain at least one exercise which shows how misleading it can be i
138.
▲
by
phkamp
7y ago
I guess it is that season again ? :-) This article seems to pop up about every other year, and pretty much garner the same general reactions every time. A lot of CS-majors immediately go in to defensive mode, starting to spew O(blablabla) f
139.
▲
by
phkamp
7y ago
How can this even be a question 20 years after FreeBSD Jails ? https://papers.freebsd.org/2000/phk-jails/
140.
▲
by
phkamp
7y ago
Seconded! I worked on a SW-project there in the late 1980-ies (Moving the European Parliament from OSI to TCP/IP) and it was a strange and wonderful place indeed. And yes, very good food, I gained four kg in the first two months :-) Bu
141.
▲
by
phkamp
7y ago
To be totally honest, I have no idea what order things happened in there, but it would be very Commodore like to reuse the molds for the plastic that way. We have never compared the C900 physically to the A2000 in datamuseum.dk, we should d
142.
▲
by
phkamp
7y ago
Come to think of it, I was employed by Commodore (Danmark) A/S precisely 35 years ago this week.
143.
▲
by
phkamp
7y ago
That is very far from the truth, and the truth was nowhere as simple as that either. Commodore was a very serious and successful supplier of small business computers with the 8xxx and 82xx series. The main problem was that in this segment C
144.
▲
by
phkamp
7y ago
By and large, Commodore invented the "double-burger" tax-shelter, and discovered to their dismay that it was very hard to funnel the "liberated" money back into the company for investments. The lack of a vision going for
145.
▲
by
phkamp
7y ago
The reason the C900 were cancelled was that Commodore simply didn't have the resources (money, facilities) to do both that and the Amiga.
146.
▲
by
phkamp
7y ago
I was employed by Commodore Denmark in 1984 to become their UNIX wizard for the CBM900, and I'm part of datamuseum.dk. The 900 was very much a US project, Germany wanted the PCs. The C900 prototypes were manufactured in Germany however
147.
▲
by
phkamp
7y ago
Yes, the FOSS industry needs to grow up about software quality. It is natural to have very expensive checks in development and test-environments, they help and aid development and QA to no end, and of course they should be disabled in produ
148.
▲
by
phkamp
7y ago
No, you would put the assert inside the VOS_memcpy_s() implementation, and you would not make that a library function, but a static inline function, so the compiler can see the arguments every time it is called. As for disabling asserts in
149.
▲
by
phkamp
7y ago
I think the analysis glosses over compile time checks. Take the "VOS_memcpy_s" function they condemn for not checking one of the arguments on page 35. If the source contains a check that the destination length is no less than the
150.
▲
by
phkamp
7y ago
Actually it is not _that_ different. It is similar how you can move constitutional questions from state to federal court in the USA, with the main difference being that EU does not have federal circuits of courts like USA does, but effectiv
More ›