Viewing profile — jvink

Working on the ability to create mixnets with sanctum [0] and its cathedrals. Sanctum already has very capable traffic analysis protections in place in the form of shroud, but bein…

Picked up hacking on sanctum again after a break - https://sanctorum.se/

I've just released sanctum 1.0.0 and am taking 2-3 weeks off from hacking on it while I work on a little dumb game to be creative in a different way.

Mostly been working on tier6 [0], which is "like" zerotier but over the sanctum protocol and fully open source (ISC licensed). Getting ready to release a 1.0.0 of sanctum [1], afte…

Working on cross-flock discovery in sanctum [1] so I can cut a 1.0 release hopefully before Christmas. I am always looking for more people to test and play with it or even review t…

Working on sanctum [0] and reliquary [1]. Soon approaching a 1.0 release for sanctum once I get my brain out of vacation mode and into hacking mode again. A lot has happened this y…

Look into sanctum [1] it's cathedral mode. You can self-host those entirely and they're only discovery nodes. Once the tunnel is up the cathedral isn't involved unless for black ke…

I am continuing work on https://reliquary.se - a VPN for the hackers - based on my fully privilege separated and sandboxed VPN sanctum ( https://sanctum.se ). It is shaping up nice…

Hello HN, I would like to announce the soft availability of The Reliquary [0]: A "VPN" service for hackers. Note that VPN is in air quotes here because it is not a traditional cons…

> (also working on OpenCVS) Not actively. It has been in hybernation for a long time. Not counting the recently-ish fixes I committed not much is happening with it.

I understand. You're not forced to use the CLI create/build/run commands for anything. They just make it easier, but you are in no way tied to this. Building the module itself can …

Author of Kore here. What fears? Care to elaborate? I'd love to hear!

For sanity sake, this build option is now NOTLS.

That's fair. Parenthesising return is a matter of readability and flavour to me. It tickles my spidey sense if it is missing. I strongly dislike declaring variables anywhere else b…

Author here. I see you picked out the few things that I consistently hear on the coding style I adopted which is based on my time hacking on openbsd. I have no real points to argue…

Thanks. I agree the BENCHMARK build option is a bit confusing. I might end up renaming it altogether.

That is great, thanks for sharing.

Correct. The accepting socket is shared between multiple workers which each have its own fd for epoll or kqueue. Because of this a form of serialising the accepts between said work…

Except you are basing yourself on the fact it creates a single worker process per connection. It does not. Workers are spawned when the server is started. Each of them deals with t…

Kore does not fork per connection. It uses per cpu worker processes which multiplex I/O over either epoll or kqueue.

It is not a forking web server. It is evented I/O with multiple worker processes. It is literally in the documentation and easily spottable in the code.