This is a quick intro with how to use lokinet with dnscrypt-proxy on ubuntu/debian based distros to secure your dns queries from spying eyes, as requested by someone on an XMPP muc.
You want to first install
# apt update # apt install dnscrypt-proxy
lokinet see this blog post on how to do that.
By default your system will want to use
dnscrypt-proxy as system resolver, this is fine as you can always forward dns for
.snode to lokinet.
/etc/dnscrypt-proxy/dnscrypt-proxy.toml you want to add an option to provide a fowarding file:
forwarding_rules = '/etc/dnscrypt-proxy/forwarding-rules.txt'
In a new file at
/etc/dnscrypt-proxy/forwarding-rules.txt'put the following forwarding rules:
loki 127.3.2.1 snode 127.3.2.1 0.10.in-addr.arpa 127.3.2.1
The first rule says to forward the
.loki gtld to lokinet …
New stable opentracker now online with announce urls:
This blog post will guide you through the process of installing lokinet using our apt repo and is aimed at people whom are just getting into linux and may not know how to do such.
If you want to learn don't copy paste, if you want it to just do stuff and don't care yeah just copy paste.
Open up a terminal, in stock ubuntu it's
control alt T.
Now we want to grab the apt repo's public keys, this is used to verify packages.
curl -s https://deb.imaginary.stream/public.gpg | sudo apt-key add -
(This requires you to enter your admin password because it is using sudo)
Next we want to add the apt repo to the system's apt repo list:
echo "deb https://deb.imaginary.stream $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/imaginary.stream.list
(This will auto detect what version …
One year has passed since working on lokinet full time and we've managed to make something that works and does stuff. The upcoming release is being held off until "stability fixes" are applied. When lokinet works it works very well, the problem we face right now is (I suspect) some lingering path handover logic errors which can be tuned out with time. I'd really like to do a release but have been to hold off until the "stability fixes" are applied. I don't know how long that will take and would rather do a release now so we can start iterating on scaling the network and handling any possible issues in that. Over all I suspect are ready for launch.
The next step in development is the mobile port, which I am dreading. The lokinet code was not made with mobile in mind, it was made to …
i2pd (I2P Daemon) is a full-featured C++ implementation of I2P client.
I2P (Invisible Internet Protocol) is a universal anonymous network layer. All communications over I2P are anonymous and end-to-end encrypted, participants don't reveal their real IP addresses.
I2P client is a software used for building and using anonymous I2P networks. Such networks are commonly used for anonymous peer-to-peer applications (filesharing, cryptocurrencies) and anonymous client-server applications (websites, instant messengers, chat-servers).
I2P allows people from all around the world to communicate and share information without restrictions.
i2pd is licensed under the 3-clause BSD license, binary packages are available for Debian, Ubuntu, OS X, FreeBSD, Android and Windows.
Changelog for i2pd version 2.24:
Recently I happened across a bitcoin talk thread while peeking at my blog's http access log at a time when I should've been doing work instead.
I'll probably take this chance to make it very clear what llarp/lokinet is and is not and why it even exists in the first place.
I can say that, in my opinion, llarp/lokinet is
attempting to be a protocol to replace i2p.
I2P has a mountain of technical debt in their protocols that have been taking several (5+) years now to rectify. It is in fact easier to rewrite the whole thing than to rebase the protocol atop sanity. I am not the first person to suggest this by any means, nor the first to attempting it. The first attempt I have seen was the shadow protocol from 2013. For whatever reason it died off, I personally suspect it was because of …
We are most likely on schedule for an end of Q1 2019
"public release" of lokinet if all goes well in the internal testing phase.
( don't know why we are considering it a public release since the code is public already but eh... ‾\(._.)/‾ ) We have an internal code freeze in mid march and I hope to have a stable build ready.
It's been about 10 months since I started working on lokinet full time. The master branch on github has been relatively stable for 2 months and work on the staging branch is very heavy. We have currently 855 test cases across 95 test suites and we're not even close to full test coverage. You can generate a progress report on unit test converage as of now (March 2019) here. My personal goal is to get at least 85% coverage on the code base …
my unofficial static arm build for i2pd 2.23.0 is up here.
make sure to check the signature and verify the hash
the build was compiled with
-Os and stripped for smaller size, so you may have better speed on systems without speculative execution like the raspberry pi 1.
Rejoice, nntpchan 3.1.0 has been tagged.
This release is a security update so
All NODES are advised to upgrade
Download on github here and join us on IRC to peer into the main network.
we are on the following networks:
rizon: irc.rizon.net #nntpchan
freenode: irc.freenode.org #nntpchan