nenolod

118 ms·

31.
by nenolod 7y ago
That depends on that software being deployed in a timely manner. There's plenty of instances out there still on Mastodon 1.6 and 2.0 because the admin installed it 2 years ago and hasn't updated since.
32.
by nenolod 7y ago
Actually a hybrid approach is the way. Nobody wants to wait hours to download GBs of new gossip to get started. Streaming the gossip is necessary to make the technology viable.
33.
by nenolod 7y ago
Mastodon at Twitter scale could be truly hilarious to see.
34.
Using OTP ASN.1 Support with Elixir(blog.dereferenced.org)
1 points by nenolod 7y ago|0 comments
35.
by nenolod 10y ago
A few of the people in that group (but none on the technical board) have been contributing to projects and then disappear once the IRCv3 bits are included. Thusly it appears from a broad glance that they had no interest in the project itse
36.
by nenolod 10y ago
Regarding the IRCv3 group: it's actually worse. Historically the IRCv3 project originated at Atheme as a project to bring some extensions to IRC in order to make it more modernized, such as the SASL binding (IRC Authentication Layer).
37.
by nenolod 12y ago
Interesting but the article does not really explain the thesis statement at all...
38.
by nenolod 12y ago
It's very specialized and last time I looked at it, it was based on Qt types and other ugly things. It would not be realistic as an alternative protocol for IRC itself.
39.
by nenolod 12y ago
It sends some channel messages after the JOIN. The new IRCv3.2 specification (being formally ratified across vendors soon!) adds a BURST type to make the protocol transactional which will allow displaying the messages in the right order
40.
by nenolod 12y ago
We are planning to bring some experimental JSON-based transport for 3.3 which will allow us to eventually start transitioning to considering IRC events in an intermediate representation. The key thing is going to be getting the client auth
41.
by nenolod 13y ago
None.
42.
by nenolod 13y ago
His business model is, he has a bunch of cabinets colocated in a datacenter I operate in Dallas. And he financed it with his bitcoin winnings, I guess.
43.
by nenolod 13y ago
This has layer3 properties, such as connection rate, and was most likely mitigated using layer 3 filtering.
44.
by nenolod 13y ago
Direct peering with the eyeball networks helps a lot, as you can use smaller links (and thus, smaller scrubbing devices) on them. I do not believe that it sacrifices network neutrality, really. Comcast is really in a class of it's own
45.
by nenolod 13y ago
The Github attack was a volumetric flood, this most certainly has layer 3 properties. The post clearly discusses layer7 floods which do not have layer3 properties (such as slowloris.pl, rudy.pl, etc.) which are uncommon. It would be a safe
46.
by nenolod 13y ago
Usually it's some kid who wants to show off their botnet (or, more likely their $5 booting service investment) to their friends on hackforums. I deal with this crap all the time.
47.
by nenolod 13y ago
Actually, this is not really true. Writing a fully-fledged RFC1459 parser that handles all potential corner-cases in a secure and efficient manner is actually very difficult. By moving the essence of the protocol to an encapsulation that i
48.
by nenolod 13y ago
BuyVM. http://lowendtalk.com/discussion/20847/buyvm-lies-cheats-ste... Whether they are doing so dishonestly is a subjective question though. I changed the README a little.
49.
by nenolod 13y ago
The point here is that the information in /proc/cpuinfo is virtualized, and therefore may not reflect reality...
50.
by nenolod 13y ago
This is more about the "I put a VPS inside your VPS" situation, which is common amongst the providers offering Virtuozzo at budget pricing. In that case, we do not have files in /proc to look at, we have to do it the hard way
51.
by nenolod 13y ago
The point of the project in this case is to detect the hypervisor from within a child container (which has a virtualized /proc and /sys). Hosting providers do this with their Virtuozzo products so they can take advantage of memory
52.
by nenolod 13y ago
Honestly the usage of SolusVM, WHMCS etc (i.e. things written in PHP which have no business being written in at least, the way a PHP typically is written) has been the main security problem of the entire industry. We need more things like
53.
by nenolod 13y ago
Alpine 2.4, 2.5 and 2.6 are not vulnerable even though PERF_EVENTS is enabled: [5126545.172128] BUG: unable to handle kernel paging request at ffffffff1de68048
54.
by nenolod 14y ago
Lets be honest here. How frequently do you think a company changes processors?
55.
by nenolod 14y ago
Since Dodd-Frank, debit cards and credit cards have the same liability protections.
56.
by nenolod 14y ago
Proof?
57.
by nenolod 14y ago
Last 4 is all you need to wreak some serious havoc though. Service cancellations and whatnot...
58.
by nenolod 14y ago
Except that LISH passwords were plaintext...
59.
by nenolod 14y ago
Unfortunately it is tied to the merchant. :(
60.
by nenolod 14y ago
Except you know, system memory when the key material is unlocked... unless you really believe someone is sitting there typing in the passphrase for each non-batch CC transaction, because I do not.

More ›