SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-16-2008, 08:10 AM
| ||||
| ||||
 Re: pkg_add and EPSV Marc Espie <espie@lain.home> wrote: > In article <5jl229F40urU1@mid.individual.net>, > Helmut Schneider <jumper99@gmx.de> wrote: >>Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>> Helmut Schneider <jumper99@gmx.de> wrote: >>>> Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>>>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>>> my firewall does not know EPSV but tries to parse it. As a result it >>>>>> blocks passive ftp connections using EPSV (PASV works fine). >>>>>> What can I do? >>>>>> I tried to 'export FETCH_CMD=$(which wget)' but it seems ignored (ps >>>>>> auxww still shows 'ftp -o - ...'). Can I use .netrc to disable EPSV? >>>>>> Anything else? >>>>> From ftp(1): >>>>> -E Disables EPSV/EPRT command on IPv4 connections. >>>> If I set FETCH_CMD to "ftp -E" and run pkg_add (-r): >>>> Can't exec "/usr/bin/ftp -E": No such file or directory at >>>> /usr/libdata/perl5/OpenBSD/PackageRepository.pm line 515. >>>> can't run ftp at /usr/libdata/perl5/OpenBSD/PackageRepository.pm line >>>> 515. >>> So use /usr/local/bin/ftp-no-epsv: >>> #!/bin/sh >>> exec ftp -E "$@" >>Of course that works fine but isn't suitable for all machines here. > Why is it a problem ? I don't want to copy to many scripts to the machines. Some of them are 'friendly' but not mine. At that point IMO it is easier/more transparent to use an already existing wget/ncftpget/... instead of providing a second script. If it would be possible to use pkg_add -r/u together with 'exec ftp -E "$@"' within only one single script I would love to use it but I think it isn't. > Requiring FETCH_CMD to be an executable, script or otherwise, was a > conscious decision. No doubt about that. > *really* need it. Like, if your installation doesn't deal with EPSV at > all, adding the -E to the pkg_add code in selected places is starting to > look like a good idea to me. I would agree if it is only one single machine or all that machines were under my desk. But there are several machines which I only touch from time to time and I do not want to risk pkg_add to be replaced by the next rebuild (who ever rebuilds). -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn      |
|
02-16-2008, 08:10 AM
| |||
| |||
| Re: pkg_add and EPSV Helmut Schneider <jumper99@gmx.de> wrote: > Marc Espie <espie@lain.home> wrote: >> In article <5jl229F40urU1@mid.individual.net>, >> Helmut Schneider <jumper99@gmx.de> wrote: >>>Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>> Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>>>>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>>>> my firewall does not know EPSV but tries to parse it. As a result it >>>>>>> blocks passive ftp connections using EPSV (PASV works fine). >>>>>>> What can I do? >>>>>>> I tried to 'export FETCH_CMD=$(which wget)' but it seems ignored (ps >>>>>>> auxww still shows 'ftp -o - ...'). Can I use .netrc to disable EPSV? >>>>>>> Anything else? >>>>>> From ftp(1): >>>>>> -E Disables EPSV/EPRT command on IPv4 connections. >>>>> If I set FETCH_CMD to "ftp -E" and run pkg_add (-r): >>>>> Can't exec "/usr/bin/ftp -E": No such file or directory at >>>>> /usr/libdata/perl5/OpenBSD/PackageRepository.pm line 515. >>>>> can't run ftp at /usr/libdata/perl5/OpenBSD/PackageRepository.pm line >>>>> 515. >>>> So use /usr/local/bin/ftp-no-epsv: >>>> #!/bin/sh >>>> exec ftp -E "$@" >>>Of course that works fine but isn't suitable for all machines here. >> Why is it a problem ? > > I don't want to copy to many scripts to the machines. Some of them are > 'friendly' but not mine. At that point IMO it is easier/more transparent to > use an already existing wget/ncftpget/... instead of providing a second > script. > > If it would be possible to use pkg_add -r/u together with 'exec ftp -E "$@"' > within only one single script I would love to use it but I think it isn't. If you have a home directory, place the script there. If you do not have one, then what are you doing on that box? >> *really* need it. Like, if your installation doesn't deal with EPSV at >> all, adding the -E to the pkg_add code in selected places is starting to >> look like a good idea to me. > > I would agree if it is only one single machine or all that machines were > under my desk. But there are several machines which I only touch from time > to time and I do not want to risk pkg_add to be replaced by the next rebuild > (who ever rebuilds). Okay, that makes sense. |
|
02-16-2008, 08:10 AM
| ||||
| ||||
| Re: pkg_add and EPSV Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: > Helmut Schneider <jumper99@gmx.de> wrote: >> Marc Espie <espie@lain.home> wrote: >>> In article <5jl229F40urU1@mid.individual.net>, >>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>>>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>>> Joachim Schipper <jdNoOtSPAMschipper@math.uu.nl> wrote: >>>>>>> Helmut Schneider <jumper99@gmx.de> wrote: >>>>>>>> my firewall does not know EPSV but tries to parse it. As a >>>>>>>> result it blocks passive ftp connections using EPSV (PASV >>>>>>>> works fine). What can I do? >>>>>>>> I tried to 'export FETCH_CMD=$(which wget)' but it seems >>>>>>>> ignored (ps auxww still shows 'ftp -o - ...'). Can I use >>>>>>>> .netrc to disable EPSV? Anything else? >>>>>>> From ftp(1): >>>>>>> -E Disables EPSV/EPRT command on IPv4 connections. >>>>>> If I set FETCH_CMD to "ftp -E" and run pkg_add (-r): >>>>>> Can't exec "/usr/bin/ftp -E": No such file or directory at >>>>>> /usr/libdata/perl5/OpenBSD/PackageRepository.pm line 515. >>>>>> can't run ftp at /usr/libdata/perl5/OpenBSD/PackageRepository.pm line >>>>>> 515. >>>>> So use /usr/local/bin/ftp-no-epsv: >>>>> #!/bin/sh >>>>> exec ftp -E "$@" >>>>Of course that works fine but isn't suitable for all machines here. >>> Why is it a problem ? >> I don't want to copy to many scripts to the machines. Some of them are >> 'friendly' but not mine. At that point IMO it is easier/more >> transparent to use an already existing wget/ncftpget/... instead of >> providing a second script. >> If it would be possible to use pkg_add -r/u together with 'exec ftp -E >> "$@"' within only one single script I would love to use it but I >> think it isn't. > If you have a home directory, place the script there. If you do not have > one, then what are you doing on that box? I'm a very nice guy and help friends whenever they break something. I also set up a package server, compile and provide packages for them, patch their systems, upgrade their systems, and *sometimes* I get tickets for Bayern München for my work.  )-- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn |
Linear Mode
