I'm running 6.4-stable amd64 on my laptop. I have a repository on my webserver where I keep custom packages (pardon the "gnuser" in url--the domain predates my openbsd conversion). Accessing the repository requires https, username, and password. Setting TRUSTED_PKG_PATH to my repository has no effect, forcing me to use PKG_PATH and sign my own packages. Observe:
# cat /etc/installurl https://cdn.openbsd.org/pub/OpenBSD # TRUSTED_PKG_PATH=https://bruno:[email protected]/openbsd-custom/6.4/packages/amd64 # PKG_PATH='' # pkg_add myscripts Can't find myscripts # TRUSTED_PKG_PATH='' # PKG_PATH=https://bruno:[email protected]/openbsd-custom/6.4/packages/amd64 # pkg_add myscripts myscripts-1.0: ok I searched the mailing list for "TRUSTED_PKG_PATH" and didn't find anything like this described. Did I find a bug?
