stargrave

http://www.stargrave.org/ -- various articles, software development, blog

http://blog.stargrave.org/russian/ with more than 4.8k of posts, but on russian.

My blog (http://blog.stargrave.org/russian/) initially also used Git as a storage, where each commit is a post, and its log message is the content itself. If I add gitweb/cgit, when it will also feature web interface and Atom feed automatically. Later I added my own rendering engine to it: http://www.sgblog.stargrave.org/ for efficiency and automatic transparent gopher/gemini protocols support. Each post also can have some dynamic tags/topics attached, that are stored in git's notes branch. And later I also added ability to leave comments, by sending email message, that is committed in another git-note branch in the form of recfile (https://www.gnu.org/software/recutils/) plain-text comment. Everything is plain text, can be used with Git solely, but has an engine for better rendering and wider protocols support.

I used GNU/Linux for 7-8 years, but returned back to FreeBSD using it for dozen of yeas. On each home and work PC, on each VPS and server I rule. Only that OS. http://www.stargrave.org/WareHistory.html http://www.stargrave.org/Ware.html

More clones: https://www.brendangregg.com/blog/2006-01-12/brendan-clones....

My 12+ years old website: http://www.stargrave.org/ Currently it is built as a Texinfo document. Previously I used reStructuted Text (Sphinx), Vimwiki, Gopher-compatible Perl scripts, FTP-viewable READMEs and static HTMLs. Contains much more data than even social networks will ask from people.

There is my collection of hundreds of personal and IT-related blogs/homepages: http://www.stargrave.org/LinksCatPersonal.html

One of redo's implementations (on Go) has complete documentation on the whole redo build system (applicable to most (all?) redo-s) usage: http://www.goredo.cypherpunks.ru/Usage-rules.html

And again noone forces you to use multiple files too :-). You can literally have just single default.do file for the whole project. apenwarr/redo somewhere explicitly noted that. Separate .do files are only for convenience and ability to automatically depend on target's build rules independently from others, that Make just do not do at all.

Nobody forces you to use any kind of shell with redo. Its .do files can be anything you want: ELF object files, shell scripts, Perl, Python, whatever, just make it executable and obey trivial simple rules (stdout and three arguments).

I have got many URLs in newsboat: wc -l ~/.newsboat/urls -> 367. And nearly all of them are shared in recfile: http://www.stargrave.org/links.rec that is linked from http://www.stargrave.org/Links.html. Mostly it contains various personal blogs.

FidoNet is still living, however it lacks at least strong authentication and data confidentiality (no crypto used at all). But it shows that people could be capable of creating global networks without unwanted third-parties.

For building store-and-forward networks I created NNCP several years ago and lack of connectivity, censorship (making no connection links) are one of the issues it aims to solve: http://www.nncpgo.org/Use-cases.html

Personally I used Python's tnote program, but, because of Python, it worked pretty slowly. So I rewrite on pure POSIX shell and it serves me for nearly ten years: http://www.git.stargrave.org/?p=t.git;a=blob;f=t

Comparing to author's solution, it gives ability to briefly list notes, use multiple "namespaces", quickly add (without invoking the editor), delete or modify each specified note. Also there is no bashism and it works out of box on *BSD (that lacks bash) and GNU systems.

No, multiple output is not covered. gored passes on all my projects, even containing complicated redo-stamp/redo-always dependencies the same as apenwarr/redo. Not everything is passed in its testsuite, but I did not dig why. In practice it is complete replacement for my needs with the same behaviour.

SGBlog (http://sgblog.stargrave.org/) is Git-backed blogging engine with gopher protocol support (for making plogs). Out of the box, just with inetd.

And my answer to them: https://lists.gnu.org/archive/html/libreplanet-discuss/2019-...

I have posted link on HN to Dataforge UUCP because I have been interested in store-and-forward networks for a long years. All my email passing between notebook and my email servers used UUCP-over-SSH for years. But soon I create NNCP (http://www.nncpgo.org/) project and totally moved all my email/files store-and-forward networks to it. Possibly it could be interested to you.

Done in https://news.ycombinator.com/item?id=14190970

Anonymity is not the goal, because it is another separate task.

NNCP contains nncp-daemon and nncp-caller that work with online protocol. It uses Noise protocol: http://noiseprotocol.org/ (Noise-IK). So ratcheting as Signal does is already applied. http://www.nncpgo.org/Sync.html

Really interesting project! Must look on it much more closer! Thanks for the pointer.

Unfortunately NNTP(like) is the only thing I have never touched at all. I have several years of experience with FidoNet's echomail (this is like NNTP), but today I see that most of discussion is done in mailing lists and I have got no usecases I really could use with something like NNTP (and that is disappointing, because I really like that echomail/news nature).

Thanks for mentioning that. I forgot to remove that link. There is no mirror on Github anymore.

>Any projects that attempted to do this sort of overlay for UUCP?

I have met only manual creation of SSH/stunnel tunnels. So did I for many years.

For example http://www.cypherpunks.ru/pygost/Download.html page contains instructions how to receive the key. You can get it using either maillist, website, DNS, keyservers. And you can use various DNS servers and transport routes via Tor. There is plenty of options. And this key is signed with another one containing many signatures. Of course there is no full guarantees, but at least you have to do it just once and then conveniently do tarballs verifying. With TLS you have to do it everytime, all the time you visit and connect to the server.

Moreover how can you "transfer" the trust to other people? If you proxy/give tarball to someone else, then how can you prove that you did not tamper it? Again, with detached signatures people knowing public key can authenticate it, without connecting to Internet. With TLS there is only single distribution point (TLS website) that can not transfer trust to someone else.

What CA should be used for certificate issuing? Paid one? Not an option if you do not want to support PKI business model (it is business, not security). CAcert.org? Modern browsers and operating systems does not include its certificate too. So anyway you have to get its public key too somehow.

So, TLS has the same problem of getting the public key and is less convenient in use, requiring TLS-aware webserver (instead of cheap providers with static pages hosting), without ability to transfer trust (send signature separately) to someone else. OpenPGP keys (for www.cypherpunks.ru websites), comparing to CA ones, can be received with several (!) keyservers (many of them replicates between themselves), several (!) DNS servers (listed as NS record), through various transports (VPN, proxy, Tor) to one of webservers (listed as A/AAAA record).

But OpenPGP detached signatures, that are isolated and does not depend no transport protocols (TLS), defend you from all that kind of MitM attacks, because they are point-to-point (directly from developer to end-user), without depending on any third-party (like CA issuing TLS certificates, DNSSEC provides, intermediate DNS proxies that must not strip DNSSEC off, and so on).

Maybe I misunderstood you, but http://www.cypherpunks.ru/gost/enVKO.html VKO 34.10-2001 is ECDH analogue. It uses two 256 or 512-bit elliptic curves keypairs for deriving common shared 256-bit key. It is Diffie-Hellman, like curve25519, with at least 128-bit security margin.

http://www.cypherpunks.ru/gost/en3410.html GOST R 34.10-2001/2012 are digital signatures based on elliptic curves. Just like ECDSA.

PKI is a business model. That download page suggests you to verify downloaded tarballs with OpenPGP key, or visit Git repository to look for signed (OpenPGP again) tags there. Of course you have to setup some kind of trust for verifying keys. If your browser shows you such kind of errors, then seems that you do not trust CAcert.org used for certificate creation. You may retrieve OpenPGP keys and find signature you may trust. PKI (HTTPS) is single point of trust, OpenPGP provides much more ones.

No, it does not. GOST algorithms usage is a must inside government structures without any exceptions.

syncer works on block level, with raw byte sequences. It knows nothing about file systems. Everything is limited with sequential read/write speeds of your hard drives.

It takes blocksize-size memory block for each CPU in your system. I have got 4 CPUs and work with 2 MiB blocks: program will take 8 MiB of RAM.