Subject: feature proposal: sftp support for pkg_add
To: None <firstname.lastname@example.org>
From: Lasse Kliemann <email@example.com>
Date: 10/29/2005 02:45:14
Content-Type: text/plain; charset=us-ascii
I find the ftp support in pkg_add (via PKG_PATH) extremely useful. =20
Unfortunately, I cannot open my private repository of binary packages to th=
world, because it contains packages that may not be distributed in this way=
(djbdns for example). The most comfortable solution would be to use sftp an=
public key authentification instead of ftp.
I know that ftp also allows authentification. However, I do not want to run=
ftp server as root. Ok, likely, one will find an ftp server that allows som=
kind of authentification even when not running as root. But then, still,=20
passwords are sent in clear text, AFAIK.
The sftp solution would be much cleaner.
Unfortunately, I failed in my attempt to hack sftp support into pkg_add. Bu=
maybe this is an easy task for someone who is more familiar with the code o=
pkg_add than I am? Maybe other users are interested in this feature as well?
Maybe there is a completely different solution to my problem? First copying=
over all binary packages to a local directory is suboptimal, because it suc=
up a lot of bandwidth. Not all packages in the repository are needed on eve=
machine of mine.
In Linux, one could use sshfs to make the repository visible in a local=20
directory. But I am unaware of anything similar to sshfs in *BSD. NFS is=20
available, but AFAIK this should not be used without IPsec (at least not ov=
the Internet). Anyone knows a good tutorial how to configure IPsec and NFS?
Thanks for your advice!
All the best,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
-----END PGP SIGNATURE-----