On Fri, Mar 6, 2009 at 4:18 PM, jaalto <jari.aa...@cante.net> wrote: > The apt-p2p(8) manual page instructs to use: > > deb http://localhost:9977.... > > But in home network it is desireable to use CNAMEs for services. Let's dat > this > is named apt-p2p and we use: > > deb http://apt-p2pt:9977....
Why? You can only access the apt-p2p daemon from an apt process running on the same host, so what is the advantage of using a CNAME? I check for the 'localhost' from the connecting host to verify that the host is allowed to connect to apt-p2p as an apt client to request and download packages. > [at localhost running apt-p2p service; which is also CNAME host apt-p2p] > $ apt-get update > W: Failed to fetch > http://apt-p2p:9977/ftp.fi.debian.org/debian/dists/testing/non-free/source/Sources > 404 Not Found > ... > $ lynx http://apt-p2p:9977 > <no problems, statistic page is shown> Anyone can access a statistics page, there is no check. Try instead lynx http://apt-p2p:9977/ftp.fi.debian.org/debian/dists/testing/non-free/source/Sources which will fail, I think. > The use of CNAME doesn't seem to work, although apt-p2pt answers to > ping and is defined in 192.168.1.x The documentation is missing about > information how CNAME could be used instead of 'localhost'. I guess you can't use CNAMEs. I don't think it worth trying to reimplement the verification that this is a localhost by querying the input CNAME, just to satisfy an unusual case such as this. Feel free to convince me otherwise. Thanks, Cameron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
