majke

37 ms·

421.
by majke 10y ago
Couple of things. First, I don't think that's true nowadays. The discussion points that this (not restoring DF on signal return) is a kernel bug and should be fixed: https://lkml.org/lkml/2008/3/5&#x
422.
Intel Memory Protection Extensions – Linux Support(01.org)
1 points by majke 10y ago|0 comments
423.
by majke 10y ago
This is awesome. I thought it's closed source. I wonder how close it is to the hardware. Can I assume that whatever is parsed by XED is going to be parsed in the same way by real CPU's?
424.
It ain't about the callbacks, it's about the flow control (2013)(idea.popcount.org)
1 points by majke 10y ago|0 comments
425.
by majke 10y ago
Right. Assuming it was SYN floods, and spoofed IP addresses, do you imply that Cloudflare should send back 400gbps of SYN+ACK syn cookies packets to the wide internet?
426.
by majke 10y ago
Good brief intro article. At some point I tried to get deeper and understand ptrace(2) syscall, the technology behind strace command line tool. I wrote this piece: https://idea.popcount.org/2012-12-11-linux-process-states&#x
427.
by majke 10y ago
Bitcoin mining. WPA2 brute forcing. Maybe someone will finally find the triple-des password used at adobe for password hashing. The possibilities are endless :)
428.
The brief history of Unix socket multiplexing – select(2) system call(idea.popcount.org)
2 points by majke 10y ago|2 comments
429.
In 1998 DNS had two sets of root name servers – InterNIC and AlterNIC(wired.com)
2 points by majke 10y ago|0 comments
430.
Linux libaio async I/O is only good on XFS: Qualifying Filesystems for ScyllaDB(scylladb.com)
2 points by majke 10y ago|0 comments
431.
by majke 10y ago
(I work for CF) Indeed, if you want the HTTP/HTTPS traffic to go through Cloudflare, the DNS must go through Cloudflare. There are generally two ways to set it up: a) You move your DNS auth to Cloudflare and allow it to manage it. b) Y
432.
Early History of Unix: Unix Is Born and the Introduction of Pipes (1997)(people.fas.harvard.edu)
59 points by majke 10y ago|6 comments
433.
by majke 10y ago
Sorry to chime in late, a day after this comment was added. If you set a long DNS TTL, then you will not be able to move your IP addresses quick enough. In the DDoS world, you may need to nullroute an HTTP server IP. If you do that, you ass
434.
by majke 10y ago
The complex DNS products exist for a reason. For one they can do really good geo-routing. This makes your services go faster for a global audience. Then, some of the big companies use multiple CDN's. You might want to use one CDN provi
435.
BLIT: An Early Windowed Graphic Interface from Bell Labs – AT&T Archives (1982)(youtube.com)
15 points by majke 10y ago|1 comments
436.
Bill Joy decided to become involved with a new startup Sun Microsystems (1982)(groups.google.com)
4 points by majke 10y ago|0 comments
437.
The real history of async networking(github.com)
4 points by majke 10y ago|0 comments
438.
by majke 10y ago
To my knowledge most of the C&C protocols are unsophisticated [0]. For now there is little evidence that says the bots are behind NAT's. I'm pretty sure this will come though. In the blog post I stated that there is indication
439.
by majke 10y ago
I just wanted to chime in and say thank-you. Your technical answers are always very interesting.
440.
by majke 10y ago
(I work at CF) I usually agree that spending 1h on a talk may be much. But I found this one to be really good. Matthew is both entertaining, and revealing some things that weren't public before. I'd say the 1h is worth it.
441.
by majke 10y ago
There are researchers in many companies that are actively fighting the botnets. Some links: - https://krebsonsecurity.com/2016/10/who-makes-the-iot-things... - http://blog.malwaremustdie.org/ - h
442.
by majke 10y ago
It's impossible to say if the attacker owns one beefy server or a thousand of bots.
443.
by majke 10y ago
There is evidence that IP spoofing was _not_ used in the Krebs attacks: https://twitter.com/briankrebs/status/780139030939828224 This does not invalidate this presentation though. The recent IoT attacks are a new
444.
by majke 10y ago
To wake up the audience and emphasize the message :) Also, to divide the presentation sharply between: problem statement and the solution.
445.
by majke 10y ago
This is precisely the point of this article. The only real long term solution to stop large DDoS is to stop spoofing. The only way to stop IP spoofing is to shame misconfigured networks. For that you need attribution.
446.
by majke 10y ago
You use netflow to identify the offender of course!
447.
by majke 10y ago
This is a bold statement. First, one can spoof udp packets in the same way as tcp segments. Think syn or ack floods. Second the Krebs ddos is said to generate over 600 gigs of traffic but it was not necessarily with fully established tcp co
448.
IP Spoofing(idea.popcount.org)
513 points by majke 10y ago|132 comments
449.
by majke 10y ago
People don't understand that vx32 allows you to implement scheduler in userspace. It's not 1-to-1 mapping between host process and guest process (like NaCL for example). With vx32 you can have many-guest "processes" in o
450.
SockJS protocol spec – tests and explanation in literate programming style(sockjs.github.io)
1 points by majke 10y ago|0 comments

More ›