thomashabets2

26 ms·

331.
by thomashabets2 11y ago
I'm sorry if my illustration of why there is no hypocrisy was unclear. There may be jerk behaviour. I'm not saying there isn't. I did not mean to address that part at all. I'm saying there's no hypocrisy.
332.
by thomashabets2 11y ago
Because one is saying "what you are saying is wrong" and the other is saying "you should stop talking". That's a fundamental difference. If they get hurt (big "if"), then they are still not saying "
333.
by thomashabets2 11y ago
That's why Google is so unsuccessful at scaling technical solutions, unlike you they're not forward-thinking.
334.
by thomashabets2 11y ago
Ah yes, on closer inspection on a non-phone they are quite different. You are just wrong on the no additional security though. In addition to enabling auditing, it also allows a username/password to be turned into an ssh key, so that y
335.
by thomashabets2 11y ago
https://blog.habets.se/2014/06/Another-way-to-protect-your-S... Seems like the same thing. Even written in go, too.
336.
by thomashabets2 11y ago
> As a simple example, which Hersh himself stated in this fascinating On The Media interview, how many people knew about the Bush administration’s manipulation of intelligence before the Iraq war? Hundreds? Over a thousand? Uh. Everyone?
337.
by thomashabets2 11y ago
It was most likely upping the prio of RC4, to select that. It's been a while though.
338.
by thomashabets2 11y ago
:-) I seem to remember getting 50-70Mbps with SSL on my Raspberry Pi (not RPi2). I had to tweak my cipherlist, but not to anything unreasonable insecure. The limiting factor there though was by far the USB hard drive attached. Banana Pi h
339.
by thomashabets2 11y ago
The article does say that you should check the chec— oh, it says "verify the checksum with one you downloaded from a secure place". Oh… oh no. You're right. To the author: What, pray tell, is this magical secure place that&#x
340.
by thomashabets2 11y ago
> Pure garbage. From your link: "The servers are also designed to deliver between 10Gbps and 40Gbps of continuous bandwidth utilization" So how many terabits per second are you pushing out? Oh… oh you're not? You're n
341.
by thomashabets2 11y ago
Huh. Well that's superfish. Surely the norm among big name AV is to check CAs? Or am I being naive? > I think the author is arguing here that the MITM attack wouldn't bother with encrypted traffic (which is obviously a very wea
342.
by thomashabets2 11y ago
If you don't have AES-NI, then you don't have much traffic. Otherwise you would have bought newer servers. And you therefore don't have a problem either way.
343.
by thomashabets2 11y ago
Tell this to Github. They are being Javascript DDoSed thanks to non-encrypted connections. And no, it's not "the same thing" if China forced baidu to do it directly, or if they made CNNIC forge an SSL cert.
344.
by thomashabets2 11y ago
http://lmgtfy.com/?q=define+joke
345.
by thomashabets2 11y ago
> If you're in a position and have the motivation to passively eavesdrop, you probably have the hardware to actively eavesdrop as well. Targeted, yes. Wholesale, no. When I said pay attention I was referring to the fact that in a po
346.
by thomashabets2 12y ago
"I installed OpenBSD 5.6 on my old Thinkpad x201 and much to my surprise, it just worked. [...] WiFi required a firmware update [...] I won't cover how to burn an ISO to a CD. [...] the various tweaks to config files in OpenBSD i
347.
by thomashabets2 12y ago
Ha! Indeed. I'll go back and update posts if they are no longer true. /Author
348.
by thomashabets2 12y ago
This is but one chapter of what could be a huge book on time programming, I agree. But it is a self contained advice, that should be adhered to.
349.
by thomashabets2 12y ago
> if the monotonic clock can keep such accurate timing, then everyone would just use that and NTP would not be so necessary. Stable and accurate is not the same thing. And if you have two NTP servers, and one is off (example from the art
350.
by thomashabets2 12y ago
Example code often skip error handling, because that's not the point. of course clock_gettime() should have its return value checked, just like you always check the return value of gettimeofday() and time()