public inbox for nncp-devel@lists.stargrave.org
Atom feed
From: Hadmut Danisch <hadmut@danisch•de>
To: nncp-devel@lists.cypherpunks.su
Subject: NNCP_SENDER environment for nncp-exec
Date: Sun, 14 Dec 2025 01:36:13 +0200	[thread overview]
Message-ID: <1329e383-f727-4a90-b2f8-ff77e6f17300@danisch.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

Hi,


when doing a nncp-exec, the target program at the receiver side is run 
with environments like



echo My message |
    NNCP_SELF=REMOTE \
    NNCP_SENDER=OurNodeId \
    NNCP_NICE=123 \
    /usr/sbin/sendmail -t root@localhost

as described on your web page.


That NNCP_SENDER (and NNCP_SELF) is the hex id of the sender, which in 
general is rather useless and a long random number.


Unfortunately, the neighbours are configured in the same file as the 
secret keys, i.e. /etc/nncp.hjson (if not choosing to write things in a 
big wood of separate files). So a target programm cannot (and should not 
be able) to read this and thus cannot determine the label, the human 
readable name of the sender node.


Would it be possible to pass the short names, that label used as a key 
in the neigh-Hash, as additional variables?



regards

Hadmut



[-- Attachment #2: Type: text/html, Size: 2205 bytes --]

             reply	other threads:[~2025-12-13 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-13 23:36 Hadmut Danisch [this message]
2025-12-14  0:17 ` NNCP_SENDER environment for nncp-exec Hadmut Danisch