• [ANN.] Yamn Offline Tools NG (with qrcode 4 airgapped scenarios)

    From Gabx@rasmusx@nymserv-ng.virebent.art to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 20:48:56 2026
    From Newsgroup: alt.privacy

    Announcing the release of YamnOfflineTools-NG, a standalone, pure-Go
    offline utility suite for constructing YAMN v2 mixnet packets.

    You can read about it, here: https://yamn.virebent.art/guide-yamn-offline-tools.html

    Source code:
    https://git.virebent.art/virebent/YamnOfflineTools-NG

    Best regards

    Gabx
    --
    https://contact.virebent.art
    gemini://contact.virebent.art

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gabx@rasmusx@nymserv-ng.virebent.art to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 21:45:45 2026
    From Newsgroup: alt.privacy

    Gabx wrote:
    Announcing the release of YamnOfflineTools-NG, a standalone, pure-Go
    offline utility suite for constructing YAMN v2 mixnet packets.


    #### A. nymserv-ng Registration & ANSI Terminal QR Code (ym)
    Renders the UTF-8 half-block QR code directly onto your air-gapped
    terminal console:
    ym -nym-config -alias testnym -tag TEST-01 -qr

    ### B. nymserv-ng Registration with PNG QR Export

    Exports the QR code to an image file for optical transmission:
    ym -nym-config -alias testnym -tag TEST-01 -qr-png /tmp/test_qr.png

    #### C. Outbound Anonymous Email Dispatch Template (send@)

    Generates the standard two-hop anonymity template targeting nymserv-ng:
    echo "Confidential body" | ym -nym-send -to user@example.org -s "Subject"

    #### D. YAMN v2 Onion Packet Construction (yp) Using Live Keys

    Fetch the latest public keyring and reliability stats from the Victor
    pinger:

    curl -s https://echolot.virebent.art/pubring.mix > /tmp/pubring.mix
    curl -s https://echolot.virebent.art/mlist2.txt > /tmp/mlist2.txt

    Encode a 20,480-byte armored packet through a 3-hop chain:

    echo "Secret mixnet payload" | yp -pubring /tmp/pubring.mix \
    -stats /tmp/mlist2.txt -l "yamn2,middleman,yamn" > /tmp/packet.txt
    head -n 12 /tmp/packet.txt

    #### E. Routing Loop Prevention Check (yp)

    Verify that duplicate remailers in a route are immediately flagged and
    blocked:

    echo "Loop test" | yp -pubring /tmp/pubring.mix \
    -stats /tmp/mlist2.txt -l "yamn,victor,frell"

    Expected output: Security warning: Routing loop detected! with exit code 1. Adding -allow-loop overrides the safeguard and allows packet generation.

    Best Reagrds
    Gabx
    --
    https://contact.virebent.art
    gemini://contact.virebent.art

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Billy G.@42-contact-42@pugleaf.net to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 21:01:35 2026
    From Newsgroup: alt.privacy

    Gabx wrote:
    Announcing the release of YamnOfflineTools-NG, a standalone, pure-Go
    offline utility suite for constructing YAMN v2 mixnet packets.

    Thanks for releasing it.
    Building packets offline and moving them by QR code is a nice idea.

    I compared yp/yp.go with crooks/yamn v0.2.6 (client.go and packet.go).
    The packet code is taken from there, with the same logic.
    That covers slotFinal, slotData, encodeHeader, encMessage,
    slotIntermediate and their methods.
    It also covers encodeMsg, seqIV, aesCtr and mixprep.
    The changes are small:
    panics became error messages with os.Exit(1), and Pubring became PubRing. blake2s.New became New256, which gives the same output.

    The reuse is fine but crooks/yamn is MIT licensed
    ("Copyright (c) 2014 Steve Crook").
    MIT requires that notice to be included with copies
    or substantial portions.
    The repo has no LICENSE file right now.
    The README credits only Ch1ffr3punk and says the suite was
    "redesigned from the ground up".

    Suggested fix:
    - Add crooks/yamn's MIT notice to the repo, e.g. as
    LICENSES/MIT-yamn.txt or in a NOTICE file.
    - Say in the yp.go header and in the README that the packet construction
    is derived from github.com/crooks/yamn (MIT).
    - Add the AGPL-3.0 text as LICENSE, since the README names AGPL-3.0 but
    the file is missing.

    MIT code can be part of an AGPL project, so only the notice is needed.
    Nothing else has to change.

    A small unrelated note:
    go.mod says "go 1.27", while the guide says Go 1.25 or newer.

    Since you build on crooks/yamn:
    we maintain a fork of it at https://github.com/go-while/yamn.

    crooks has been inactive for over a year,
    so we went through the code in two reviews and fixed what we found.

    Stock and fork remailers can run side by side in the same network.

    What it does differently:
    - A malformed packet or file no longer crashes the remailer.
    - A middle remailer only forwards to remailers in its keyring, without
    line breaks in the address, so a sender can't use it to mail arbitrary
    addresses or inject headers.
    - Messages larger than one packet are delivered.
    Stock clients reuse one packet ID for all chunks, so exits drop chunks
    2 and up.
    - SMTP to a configured relay verifies the certificate, with an option to
    require TLS.
    SMTP connections have timeouts.
    - The replay window is closed: ID log entries last longer than the
    maximum packet age.
    - A failed keyring download no longer overwrites a good keyring.
    - The client can merge keyrings and stats from several pingers, with a
    quorum on keys.
    - It can verify signed pinger files (minisign).
    - Key pinning: a remailer key that changes earlier than a normal
    rotation is held for 24 hours and logged before use.
    - Tor support, including .onion relays.
    - yamn refuses to run as root.

    There is also go-echolot (https://github.com/go-while/go-echolot),
    a pinger in Go meant to replace the Perl Echolot.

    It signs its output, publishes a new remailer key only after a ping
    through that key comes back, and holds unexpected key changes for 24
    hours. One instance has been pinging the public network since late October.

    Testing isn't finished yet.
    We run the fork on an 18-node private test network with three go-echolot pingers.
    Early and lost key changes pass automatically, on the pingers and on the client.
    Still open: a natural key rotation of all nodes, a mixed run with stock
    yamn nodes, and the long-term test.
    Until that's done, I wouldn't call the fork production-ready.

    Feedback from an operator would be welcome.
    --
    .......
    Billy G. (go-while)
    https://pugleaf.net
    @Newsgroup: rocksolid.nodes.help
    irc.pugleaf.net:6697 (SSL) #lounge
    TOR-IRC: ij7fmstcudrwyty5p6iloodeenur4wksovlhbyrfubat7eixplmrxvqd.onion:6667 --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gabx@rasmusx@nymserv-ng.virebent.art to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 23:36:22 2026
    From Newsgroup: alt.privacy

    Billy G. wrote:
    Gabx wrote:
    Announcing the release of YamnOfflineTools-NG, a standalone, pure-Go
    offline utility suite for constructing YAMN v2 mixnet packets.
    Thanks for releasing it.
    Building packets offline and moving them by QR code is a nice idea.

    I compared yp/yp.go with crooks/yamn v0.2.6 (client.go and packet.go).
    The packet code is taken from there, with the same logic.
    That covers slotFinal, slotData, encodeHeader, encMessage,
    slotIntermediate and their methods.
    It also covers encodeMsg, seqIV, aesCtr and mixprep.
    The changes are small:
    panics became error messages with os.Exit(1), and Pubring became PubRing. blake2s.New became New256, which gives the same output.

    The reuse is fine but crooks/yamn is MIT licensed
    ("Copyright (c) 2014 Steve Crook").
    MIT requires that notice to be included with copies
    or substantial portions.
    The repo has no LICENSE file right now.
    The README credits only Ch1ffr3punk and says the suite was
    "redesigned from the ground up".

    Suggested fix:
    - Add crooks/yamn's MIT notice to the repo, e.g. as
    LICENSES/MIT-yamn.txt or in a NOTICE file.
    - Say in the yp.go header and in the README that the packet construction
    is derived from github.com/crooks/yamn (MIT).
    - Add the AGPL-3.0 text as LICENSE, since the README names AGPL-3.0 but
    the file is missing.

    MIT code can be part of an AGPL project, so only the notice is needed. Nothing else has to change.

    A small unrelated note:
    go.mod says "go 1.27", while the guide says Go 1.25 or newer.

    Since you build on crooks/yamn:
    we maintain a fork of it at https://github.com/go-while/yamn.

    crooks has been inactive for over a year,
    so we went through the code in two reviews and fixed what we found.

    Stock and fork remailers can run side by side in the same network.

    What it does differently:
    - A malformed packet or file no longer crashes the remailer.
    - A middle remailer only forwards to remailers in its keyring, without
    line breaks in the address, so a sender can't use it to mail arbitrary
    addresses or inject headers.
    - Messages larger than one packet are delivered.
    Stock clients reuse one packet ID for all chunks, so exits drop chunks
    2 and up.
    - SMTP to a configured relay verifies the certificate, with an option to
    require TLS.
    SMTP connections have timeouts.
    - The replay window is closed: ID log entries last longer than the
    maximum packet age.
    - A failed keyring download no longer overwrites a good keyring.
    - The client can merge keyrings and stats from several pingers, with a
    quorum on keys.
    - It can verify signed pinger files (minisign).
    - Key pinning: a remailer key that changes earlier than a normal
    rotation is held for 24 hours and logged before use.
    - Tor support, including .onion relays.
    - yamn refuses to run as root.

    There is also go-echolot (https://github.com/go-while/go-echolot),
    a pinger in Go meant to replace the Perl Echolot.

    It signs its output, publishes a new remailer key only after a ping
    through that key comes back, and holds unexpected key changes for 24
    hours. One instance has been pinging the public network since late October.

    Testing isn't finished yet.
    We run the fork on an 18-node private test network with three go-echolot pingers.
    Early and lost key changes pass automatically, on the pingers and on the client.
    Still open: a natural key rotation of all nodes, a mixed run with stock
    yamn nodes, and the long-term test.
    Until that's done, I wouldn't call the fork production-ready.

    Feedback from an operator would be welcome.

    Thank you for taking the time to review the code and for the
    constructive, actionable feedback. You are completely right on all
    points regarding licensing and code provenance.

    1. Provenance and Licensing
    You correctly identified the packet construction routines in yp.go.
    While the motivation behind YamnOfflineTools-NG was to build an
    isolated, terminal-centric toolchain for air-gapped packet construction
    and QR transport, the low-level packet encoding logic (slotFinal,
    slotData, encodeHeader, encMessage, etc.) derives directly from Steve
    Crook's pioneering work in crooks/yamn (v0.2.6).

    Crediting crooks/yamn and preserving Steve Crook's MIT notice is both a
    legal obligation under the MIT license and a fundamental matter of
    cypherpunk engineering ethics. I am pushing the following changes
    immediately:
    - Adding LICENSES/MIT-yamn.txt containing Steve Crook's original 2014
    MIT copyright notice.
    - Adding a top-level NOTICE file and updating the file headers in
    yp/yp.go to explicitly state that the packet encoding routines are
    derived from github.com/crooks/yamn.
    - Adding the official AGPL-3.0 LICENSE file to the root of the
    repository, properly documenting the dual inclusion.
    - Updating the README to credit Steve Crook alongside Ch1ffr3punk.

    2. Go Version Discrepancy
    Thanks for catching the "go 1.27" in go.mod. That was an oversight
    during local toolchain experimentation. I have normalized go.mod to go
    1.25 to match the documentation and ensure smooth compilation on current
    stable Go distributions.

    3. The go-while/yamn Fork
    The review and fixes you completed on https://github.com/go-while/yamn
    are impressive and sorely needed. In particular:
    - Fixing the multi-packet delivery bug (where reusing packet IDs caused
    exit nodes to drop subsequent chunks) resolves a long-standing headache
    for large payloads.
    - Defending middle remailers against address injection and arbitrary
    mail forwarding is essential for keeping operator nodes off spam blocklists.
    - Hardening against malformed packet panics, enforcing non-root
    execution, and adding native Tor/.onion transport bring the remailer
    codebase up to modern operational security standards.
    - Key pinning and quorum-based keyring merges solve real metadata and
    trust vulnerabilities in the pinger ecosystem.

    I want to make sure YamnOfflineTools-NG stays fully compatible with both
    stock networks and go-while/yamn. I will inspect your chunking and
    packet ID handling to ensure yp generates packets that take full
    advantage of your multi-packet delivery fixes.

    4. go-echolot and Pinger Modernization
    A pure-Go replacement for Perl Echolot
    (https://github.com/go-while/go-echolot) is a massive leap forward.

    Verifying loop pings before publishing keys and applying a 24-hour hold
    on abrupt key rotations are exactly the right defensive heuristics.

    5. Collaboration and Testing
    I would be very glad to collaborate. I am interested in testing YamnOfflineTools-NG against your 18-node test network and exchanging operational feedback on go-while/yamn and go-echolot.

    Let me know the best channel to coordinate (via this thread, email, or
    git tickets). Once again, thank you for the sharp peer review and for revitalizing the YAMN mixnet ecosystem.

    Best regards,

    Gabx
    --
    https://contact.virebent.art
    gemini://contact.virebent.art

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gabx@rasmusx@nymserv-ng.virebent.art to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 23:49:32 2026
    From Newsgroup: alt.privacy

    Gabx wrote:
    - Hardening against malformed packet panics, enforcing non-root
    execution, and adding native Tor/.onion transport bring the remailer
    codebase up to modern operational security standards.

    A quick technical correction to my previous post regarding Tor:

    While Tor/.onion helps with NAT traversal and local firewall bypass, low-latency onion routing is fundamentally obsolete against a planetary controller.

    Without packet batching, mixing delays, or continuous cover traffic, Tor
    cannot resist end-to-end timing and traffic correlation.

    The real defense-in-depth is pairing YAMN with modern mixnets like the
    Nym Network (Sphinx packets, Poisson delays, and loop cover traffic) to
    achieve genuine network-level metadata privacy against a global adversary.

    Keep up the good work

    Gabx
    --
    https://contact.virebent.art
    gemini://contact.virebent.art

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Yamn Remailer@noreply@mixmin.net to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Mon Nov 9 23:44:03 2026
    From Newsgroup: alt.privacy

    Gabx once wrote:

    The real defense-in-depth is pairing YAMN with modern mixnets like the
    Nym Network (Sphinx packets, Poisson delays, and loop cover traffic) to achieve genuine network-level metadata privacy against a global adversary.

    https://github.com/Ch1ffr3punk/nscw
    https://github.com/Ch1ffr3punk/Mixfit

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Billy G.@42-contact-42@pugleaf.net to alt.privacy.anon-server,alt.privacy,alt.cypherpunks on Tue Nov 10 00:14:42 2026
    From Newsgroup: alt.privacy

    On 11/9/26 22:36, Gabx wrote:
    5. Collaboration and Testing
    I would be very glad to collaborate. I am interested in testing YamnOfflineTools-NG against your 18-node test network and exchanging operational feedback on go-while/yamn and go-echolot.

    Let me know the best channel to coordinate (via this thread, email, or
    git tickets). Once again, thank you for the sharp peer review and for revitalizing the YAMN mixnet ecosystem.

    Two options: join my IRC or you set one up and we link. https://github.com/ergochat/ergo/releases/tag/v2.19.1

    Not sure what your agent wants to test against our test network.
    I've sent a test message with yp via classic yamn and it worked.

    Put your code on github, at least as a backup. Local git is meh.
    If you want, send me an access to your git and let's burn token!
    --
    .......
    Billy G. (go-while)
    https://pugleaf.net
    @Newsgroup: rocksolid.nodes.help
    irc.pugleaf.net:6697 (SSL) #lounge
    TOR-IRC: ij7fmstcudrwyty5p6iloodeenur4wksovlhbyrfubat7eixplmrxvqd.onion:6667 --- Synchronet 3.22a-Linux NewsLink 1.2