ahf

8 ms·

1.
by ahf 8y ago
Have a look at Katzenpost. They are trying to build a modern, high-latency, mix network. https://katzenpost.mixnetworks.org/
2.
by ahf 9y ago
Speaker here. I'll happily answer questions that might be, but I'm at a festival so being AFK and around other lifeforms is prioritised :-) The slides are also available at: http://hapy.0x90.dk/~ahf/talks&#x2F
3.
by ahf 12y ago
I think it would be much nicer if the browser vendors started pushing for DANE + DNSSEC. Together, they are a quite neat combo and we wouldn't have to pay for certificates anymore.
4.
by ahf 13y ago
No, nobody can easily know this - Quakenet's probably still the target of DDoS. Aren't we getting to the point where we more or less must assume that these kind of things happens? I mean, taking into account all the news we have s
5.
by ahf 13y ago
Non-plaintext authentication mechanisms are a good start - it's an extra layer of security that you add to your system. Having SSL between your servers is also an extra layer of security. Having client-to-server SSL is, once agai
6.
by ahf 13y ago
Not the same as Freenode does, but Quakenet does have services, yes.
7.
by ahf 13y ago
I'm sorry, but said article have already been brought up multiple times in #dev and people are starting to understand how it doesn't hold water anymore. I break into any discussion I see on IRC where someone posts a link to this a
8.
by ahf 13y ago
It's not true that this is up to the clients authors alone to do this work, and it's not fair for the users to tell them that you are awaiting client adoption of various technology, when the current Quakenet ircd implementation is
9.
by ahf 13y ago
Other networks have adopted SSL much earlier and I simply refuse to believe that Quakenet's problem is CPU related. I'm not saying that a network should require all of its users to use SSL, but I do think that it's should be
10.
by ahf 13y ago
Albeit unrelated, I wonder when Quakenet is going to realise that SSL for IRC, both server-to-server, but also client-to-server, is a must have in the year 2014, if you are truly care about your users privacy.
11.
Irssi 0.8.16-rc1 Released with DNSSEC DANE Support(irssi.org)
2 points by ahf 13y ago|0 comments
12.
by ahf 13y ago
It's true that we still haven't secured the connection between the user and his ISP's DNS server, which I agree is a problem. DNSSEC only helps between the DNS servers themselves. We are now down to either a) run your own DNS
13.
by ahf 13y ago
In the recent weeks, there have been a lot of discussions about security on IRC and the use of web-based IRC clients in particular. The general opinion appears to be that people really don't give a rat's ass about securing themsel
14.
by ahf 13y ago
Yeah, that's true; DANE does not add anything to the encryption of the protocol itself. The point of this is to, hopefully, slowly get people to start actually verifying certificates instead of just randomly assuming that they are secu
15.
by ahf 13y ago
Interesting. Line skipping is by far the most annoying problem that I face when I have to read after a long day; especially on a screen.
16.
by ahf 13y ago
Kiddies are DDoS'ing to annoy other users and to prove that they are capable of taking down the nodes. All servers on the largest IRC networks are very well connected to the internet and servers that are not, wont be able to last long on th
17.
by ahf 13y ago
It is an IRC term for a "kill line". If your host tuple (nickname, username and hostname) somehow matches the kill line, your connection to the server will be closed with a message on why it was closed.