How to enable pkg_add for OpenBSD

OpenBSD packages are not 'signed' at all by default.

If you are using OpenBSD in commercial environment, let your employer to buy release CD. Then you will get OpenBSD release with packages on CD which you can trust :-)

Better way, and if you are using OpenBSD seriously you should have it, is to have a build server. Sync OpenBSD ports from anoncvs - here you trust ssh fingeprint which is publicly announced - then build your own ports and sign them with certificate. With tool `dpb' it should be even much easier.

OpenBSD packages is secondary interest for the project as whole.

Looks like dependencies are specified in the packing list. You can see the packing list with pkg_info -f.

So, assuming PKG_PATH is already set:

pkg_info -f XYZ | grep '^@depend' | cut -f 3 -d :

should give you the package names.

Prepending $PKG_PATH and appending .tgz to each line should give you a URL that's probably what would be downloaded, e.g. to get bash's dependencies:

PKG_PATH=http://ftp3.usa.openbsd.org/pub/OpenBSD/5.1/packages/amd64/
export PKG_PATH
pkg_info -f bash | grep '@depend' | cut -f 3 -d : | while read package; do
    echo $PKG_PATH$package.tgz
done

prints

http://ftp3.usa.openbsd.org/pub/OpenBSD/5.1/packages/amd64/libiconv-1.14.tgz
http://ftp3.usa.openbsd.org/pub/OpenBSD/5.1/packages/amd64/gettext-0.18.1p1.tgz

See also pkg_add -n and PKG_CACHE.

References:

• pkg_info(1)
• pkg_add(1)