On 2/17/26 18:51, Andrew Kloet wrote:
On 2/13/26 15:20, David Uhden Collado wrote:Here is a port for net/arti 2.0.0 Arti is a complete rewrite of the C Tor codebase, and it is currently under active development. It is written in Rust, and it is designed to be modular, reusable, and easy to audit. There was previous effort to get a port made for Arti 1.0.0 in 2022 that was dropped: https://marc.info/?l=openbsd-ports&m=166222034813901&w=2 OK?The port does not have an RC script, which is essential for this software, nor does it install the sample configuration file (arti- example-config.toml) located in the root of the arti create. I also think that if arti is added to the ports tree, a flavor should be added to the Tor browser so that arti can be used instead of tor as a runtime dependency.This is an update of my original patch. It includes an rc.d script, default configs, and a dedicated user. However there are some things to note that are not super ideal, and are a problem of the current state of the upstream arti daemon: when no config is provided, arti defaults to scanning paths such as. ${HOME}/.local/share/arti/state These default search paths can be overridden by environment variables like $ARTI_LOCAL_DATA. But as far as I'm aware it is bad practice to set these in login.conf. I instead opted to patch the default `arti.toml` config to point to the directories it needs in the /var/arti folder that I create in the port. Please let me know if there is a nicer/more standard way to go about this. Also, I'd like to request to reserve UID/GID 904 for the _arti user OK? Andrew
Sorry, I forgot to run portcheck. Also, I added the doc/ folder from the build to the packing list. Andrew
arti.tar.gz
Description: application/gzip
