Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
i336_
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
104 ms
·
721.
▲
by
i336_
10y ago
The logo failed to mirror, but everything else is intact: http://archive.is/IoYJZ
722.
▲
by
i336_
10y ago
I forgot to ask earlier: how much "worse" is OpenBSD's SMP implementation than Linux's/everyone else's? > SELinux was released in 1998. Linux was totally usable back then. I've been using it since 1995
723.
▲
by
i336_
10y ago
descended*, woops And with "did it even have any security capabilities" I was referring to Linux (just to be clear).
724.
▲
by
i336_
10y ago
> Kylin was the Chinese FreeBSD fork (if you can even call it that) started in 2001. Oh, wow, that was a while ago. I can see why they picked FreeBSD, Linux wasn't really all-around usable back then. Did it even have any security ca
725.
▲
by
i336_
10y ago
...I am not having a good brain day today. 1. In my previous comment I meant OpenSSL, not OpenSSH. 2. So I just established that Theo is the author of OpenSSH , while OpenSSL is the large pile of fail. I certainly recognize the differenc
726.
▲
by
i336_
10y ago
Unless I'm mistaken, Theo de Raadt was the author of both projects.
727.
▲
by
i336_
10y ago
Testcase: http://example.com/url/); <-- http://example.com/url/ ); http://example.com/veryveryveryveryveryveryveryloooooooooooo... <-- there is a ); at the end of this that
728.
▲
Arc bugreport: URL matching error with “.../);”
2 points
by
i336_
10y ago
|
3 comments
729.
▲
by
i336_
10y ago
I found this HN discussion from just under a year ago on pledge(): https://news.ycombinator.com/item?id=10537268 (which lists this presentation: http://www.openbsd.org/papers/hackfest2015-pledge/mg
730.
▲
The insecurity of OpenBSD (2010)
(allthatiswrong.wordpress.com)
2 points
by
i336_
10y ago
|
15 comments
731.
▲
by
i336_
10y ago
I'm curious what was wrong with QNX the company, in terms of the practical ramifications of what you're describing. I assume you were using QNX for the GC vehicle compo because of its RTOS qualities? In any case, that's aweso
732.
▲
by
i336_
10y ago
Woops, typed text/html out of habit, meant text/plain. base64 -di works just fine too.
733.
▲
by
i336_
10y ago
Arrrrrgh. Roar. QNX was cautiously courting the open source concept and venturing in the direction of shared source (with some code already available), when BlackBerry bought them and threw all of that out the window. Biggest yanked opportu
734.
▲
by
i336_
10y ago
Oh , of course, right. Misinterpreted that bit.
735.
▲
by
i336_
10y ago
But it must be said that GPU evolution, and that password cracking software developers are naturally going to go where the passwords are, that this type of simple password design does NOT work anymore.
736.
▲
by
i336_
10y ago
AFAIK: Not a limitation, but the notion that the graphical console should replace the text console on the same TTY. Kind of makes sense, but very consistency/tradition-breaking. One of those decisions that should have been implemented
737.
▲
by
i336_
10y ago
I think the "it" you refer to here would be interesting to quite a few people, I'm having a hard time finding it.
738.
▲
by
i336_
10y ago
It is now, I see 16 results.
739.
▲
by
i336_
10y ago
-F vs -f: -F figures out the new inode if the file is deleted (*notify are inode-based, if you see DELETE_SELF for a file you'll never get any more events)
740.
▲
by
i336_
10y ago
Contabo are 100Mbit but unmetered, ridiculously cheap. Reddit's main issue is that you can only do one call (via OAuth) per second. I recommend using the new(ish) "thing" call where you can get up to 100 things at once, or al
741.
▲
by
i336_
10y ago
I'm really sorry to hear that. Suggestion: put everything in an encrypted file (I think .7z is good, AFAIK .zip is very bad), send that to lots of people. If anything happens to you, it should be manageable to get the passphrase to s
742.
▲
by
i336_
10y ago
As someone who doesn't follow the cellular scene as much as I probably should, the immediate question I ask is: what is the impact of this development work from the security standpoint of (potentially stealth) voice/data intercept
743.
▲
by
i336_
10y ago
> I cannot dive into too much more detail ... since it's still sensitive information. Question: When should we start checking around for posts containing A) High-level technical overviews with some basic implementational detail B) I
744.
▲
by
i336_
10y ago
If I can get a word in on this subject, I'd like to say this: If Android is stripped completely back to minimum and rebuilt fully from source, it's arguably a trustworthy platform, but who has the time to basically do the equivale
745.
▲
by
i336_
10y ago
I'm reminded of this very amusing C++ compilation speedup trick: cat * > everything.cpp - http://stackoverflow.com/a/318495/3229684 --- Also, I tend to do all my work using a realtime-feedback model like t
746.
▲
by
i336_
10y ago
Thanks for these videos, they're real gems. I've wanted to see the foxes at the Institute for Cytology+Genetics for a very long time, and this raw footage almost puts me there. I finally see the difference between the tamed and no
747.
▲
by
i336_
10y ago
TIL, thanks for the clarification and information. Definitely filed away.
748.
▲
by
i336_
10y ago
For some reason I'd like to share this base64 data: URI. I think it might be a URL to a certain PDF. data:text/plain;base64,aHR0cDovL2F2aWF0aW9ud2Vlay5jb20vc2l0ZS1maWxlcy9hdmlhdGlvbndlZWsuY29tL2ZpbGVzL3VwbG9hZHMvMjAxNS8wNi9GLTM1JT
749.
▲
by
i336_
10y ago
That's a really cool approach, but taking the time to rip the disc means you get the extras and other features that were on the disk, along with a significantly higher quality encode of the content. If the focus is on quantity and dive
750.
▲
by
i336_
10y ago
Huh, very interesting. (And mildly obvious.) I'm curious what I should be keeping an eye out for, what sorts of people would be the most interesting to chase, etc, to maximize my chances of causing this opportunity to present itself at
More ›