Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jfindley
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
69 ms
·
271.
▲
Remote exploits in many netgear routers
(firmware.re)
2 points
by
jfindley
11y ago
|
0 comments
272.
▲
Highlight, copy, and translate text from any image
(projectnaptha.com)
2 points
by
jfindley
11y ago
|
0 comments
273.
▲
by
jfindley
11y ago
We are doing something very similar (mesos rather than k8s), also in a financial organisation. Our main issue is also security - as docker containers aren't very good at actually containing, from a security PoV, we're using SELinu
274.
▲
Libssh DH vulnerability
(libssh2.org)
4 points
by
jfindley
11y ago
|
0 comments
275.
▲
Severe Vulnerabilities Detected in FreeBSD
(blog.ptsecurity.com)
3 points
by
jfindley
11y ago
|
0 comments
276.
▲
by
jfindley
11y ago
There was an interesting experiment done on this at a DEFCON a few years back[1]. Thermite, even the more explosive copper-based variant, is pretty poor at destroying disk platters, sadly. Explosives or cutting equipment seem to be better,
277.
▲
by
jfindley
11y ago
One observation I've made over time is that arrogance is, often, a mark of inexperience. I've observed this in myself as well as countless others - on way up the learning curve you think yourself an expert and become arrogant abou
278.
▲
by
jfindley
11y ago
For very high traffic loads, I have yet to find anything that compares to wrk ( https://github.com/giltene/wrk2 ). IME, it scales better and more efficiently than anything else I've tried, short of complex distribu
279.
▲
by
jfindley
11y ago
Some feedback: 1) On chrome, this site breaks the back button. Once I get to the site, no amount of pressing 'back' will take me back to where I came from - additionally, if I visit a second page on the site, then the back button
280.
▲
by
jfindley
11y ago
Go is actually a lot more confusing about this than this than this page makes clear. a := .1; b := .2 fmt.Println(a+b) returns 0.30000000000000004 fmt.Println(.1+.2) returns 0.3 Even worse, this persists into comparisons: c := .3 a+b == c r
281.
▲
by
jfindley
11y ago
You asserted: > Paying people well doesn't bother me, and I doubt it actually bothers anybody. To which I pointed out that it might well bother some groups of people. You also asserted that: > ... has little to nothing to do with
282.
▲
by
jfindley
11y ago
A company has a finite amount of money to spend on payroll. The less you can get away with paying the low and middle level employees, the more you free up for the higher level employees. Part of the reason high-end salaries have increased
283.
▲
by
jfindley
11y ago
Mesos does now have early-stage support for persistent disks. See https://github.com/apache/mesos/blob/master/docs/persistent-... There's also technologies like flocker that will allow you do
284.
▲
by
jfindley
11y ago
This is deeply alarming, and (at least to me) very unexpected. For the minute I'm assuming that we shouldn't be changing anything right now - it seems a bit drastic to immediately abandon ECC right now based on this - but this is
285.
▲
by
jfindley
11y ago
The point of erasing the clipboard is not to protect against malicious software - as others have pointed out, this doesn't work. The point of doing this is to reduce the risk that the user accidentally pastes their password somewhere
286.
▲
by
jfindley
11y ago
What I'd really like is an all-in-one service that incorporated Docker Content Trust[0]. While I'd prefer that they'd used something a bit more mainstream (e.g. GPG), some image signing is better than none at all. Doing this
287.
▲
by
jfindley
11y ago
Atomic[0] provides this on a Fedora/CentOS + docker base, and it works very well. It's slightly more mature than the CoreOS version as there is support for sharing volumes (volumes mounted with z are sharable, volumes mounted wit
288.
▲
by
jfindley
11y ago
Note that you can upgrade the RAM on the 13" model to 16GB, although you have to do this at purchase time, it's not possible to expand later with the current model. I, personally, use a 13" with 16GB RAM and have external scr
289.
▲
by
jfindley
11y ago
Banks are sadly frequently too slow moving and bureaucratic to keep up with the rest of the world, and often don't have any good infosec people. Case in point - I recently found myself (very reluctantly and under severe protest) patchi
290.
▲
by
jfindley
11y ago
I'm not sure that's true. While I'm not a fan of the entitlement-culture that's a massive feature of large parts of the popular internet, there's more to this than simple entitlement. Demanding content for free is
291.
▲
by
jfindley
11y ago
Given how fast go code compiles, I wonder how many use-cases for interpreted Go code would be solved by a good plugin system? Certainly for the use-cases where I would use this proposal, I'd be just as happy (if not happier) with a pl
292.
▲
by
jfindley
11y ago
I wrote a PoC app [0] a while ago to do just this - allow storing and sharing of keys, with the server holding the encrypted keys never seeing the decryption key. Sharing a key involves downloading it from the server, asymetrically encrypti
293.
▲
by
jfindley
11y ago
I don't think the performance for btrfs can be considered "close". And the thing with filesystems is that the format can't really change once stable - and you get locked into an architecture that dictates an awful lot ab
294.
▲
by
jfindley
11y ago
I've run bcache-backed databases in production for about a year or so - it's been absolutely rock solid, and I'm very happy with it. We spent a lot of time prototyping basically every SSD caching tech that existed at the time
295.
▲
by
jfindley
11y ago
XFS has recently-ish (depending on your definition of recently) had a significant workover in this area. Before this, EXT4 was the king of metadata-intensive workloads. Nowadays XFS wins. I'm guessing you used the older code (rhel
296.
▲
by
jfindley
11y ago
The systemd war is probably the best thing that could have happened to ensure widespread adoption of systemd. It allowed the supporters to lump anyone with any concerns or objections in with the frothing-at-the-mouth haters, and completely
297.
▲
by
jfindley
11y ago
I'm not entirely disagreeing with your post, but there's a few comments I'd like to make. 1) HAproxy does support SPDY, now via NPN/ALPN. And you don't need http mode for this. 2) HTTP performance (and performance
298.
▲
by
jfindley
11y ago
> A big difference is that HAProxy's main balancing algorithm is "fair" I don't think that's really true - haproxy has lots of load balancing modes, none of which are called "fair". It's also very
299.
▲
by
jfindley
12y ago
> If they can access Redis they can access pre-bcrypt passwords and therefore making bcrypt's rounds completely unimportant. No. The unhashed passwords are not stored in redis. What I think you're missing is that there'
300.
▲
by
jfindley
12y ago
It's in a redis database, so it's not all that hard to get at, either, should someone compromise the system. "Not on disk" stops being such a good defence when it's stored in a semi-persistent DB. My main complaint
More ›