Re: turning off exim on port 25
On Wed, May 23, 2001 at 11:33:40PM -0700, Eric N. Valor wrote: That pretty much turns off exim altogether. Actually the script in /etc/init.d/ will start exim in stand-alone mode if you disable the listener in inetd.conf. So you will still have it listening on 25/tcp. While effective for disabling the Port 25 listen, it doesn't allow Bryan to use exim for his purposes. I think he's also using it in daemon mode rather than being run from inetd. I'm not sure whether exim will still do deliveries from the queue if you disable the tcp listener (I don't use exim), but if it does, I'd suggest shutting it off altogether. Just put an exit 0 at the top of the script. (Again I'm not sure if exim will still work correctly after that, and I don't have a box handy with exim on it to test... so try it out.) -- Jim B. [EMAIL PROTECTED]
Re: pump: no extra parameters are expected
On Sat, Jan 20, 2001 at 06:32:47AM +, Jim Breton wrote: In /var/log/daemon.log I see the following: cardmgr[163]: + /sbin/pump -i eth0 /dev/null cardmgr[163]: + pump: no extra parameters are expected cardmgr[163]: start cmd exited with status 1 Well... I found the problem. I had built a new kernel on the machine and also built the pcmcia-cs package from the upstream source, and installed it because I needed modules matching my kernel build. It didn't occur to me that the scripts in /etc/pcmcia/ it installed were totally different from the ones that were installed with potato. Anyway I worked with the scripts and basically found the fix: he tries to send command /dev/null to an sh function but that doesn't work, he needs to use eval in his function. Our scripts in potato are different and do not suffer from this problem, so I'll just file a bug report (and fix) against the upstream author. Right now I'm using the modules built from upstream source, along with a re-installed set of debian scripts, and everything is fine. Thanks for listening. ;)
pump: no extra parameters are expected
I've got potato 2.2r2 running on a Quantex laptop. Whenever I insert my ethernet card (Linksys PCMPC100), the drivers for it load successfully but pump fails to configure it. In /var/log/daemon.log I see the following: cardmgr[163]: + /sbin/pump -i eth0 /dev/null cardmgr[163]: + pump: no extra parameters are expected cardmgr[163]: start cmd exited with status 1 Any idea how to fix this? I can configure the card manually, or by running pump by hand, but I would like it to work correctly upon card insertion. (Fwiw this also happens if the card is already in the laptop when I turn it on... not that it makes any difference though.)
Re: pump: no extra parameters are expected
Please ignore, I was unaware of the debian-laptop list until just now; will re-post there. Thanks.
using -nolisten tcp with X
I have been aliasing startx to startx -nolisten tcp in my local users' .bash_profiles in order to prevent X from listening on port 6000 on startup. However, display managers (at least gdm anyway) don't care about these aliases, and furthermore I would like to make this option the system-wide default, so I'm wondering in which file I might be able to specify this option for the X server to use at every invocation? It needs to be in a config file so it won't get trashed if any X packages are upgraded. Also, under such a scheme, how would one then re-enable tcp listening for an individual X session if that were desired for some reason? Thanks. (I am not on the list currently; please copy me on replies.)
all .deb md5sums
Is there someplace on debian.org from which I can get a file or files containing the md5sums of all the packages? Not the packages' contents, but the packages themselves. I have some ISOs I got from another site (linuxiso.org) and I would like to confirm the sums of all the packages before I use them for installs. Please copy me on responses as I am currently not subscribed to debian-user. :) Thanks.
Re: Editing and storing encrypted files
On Wed, Sep 06, 2000 at 10:22:44PM +0200, Wouter Hanegraaff wrote: I have some files that I would like to store encrypted. Of course I can See also PPDD: http://linux01.gwdg.de/~alatham/ppdd.html
Re: chroot()ing a user's login
On Sun, 12 Dec 1999, William T Wilson wrote: Giving a user a chrooted home won't be an easy task. You need to have a fully functional system under there - that means the shell, libc, and all that jazz. Are you sure you can't do what you want to do with a restricted shell? I primarily want to learn how to do it for the knowledge, and I would indeed like to chroot a couple of daemons that don't provide any built-in means of chrooting themselves. I did named but that was easy, it does most of the work for me. So far I'd created the dirs I thought I would need (dev, etc, bin, home, var) and put what files in them I thought would be necessary... such as passwd, group, and a shell (sash). Now I'm prompted for my password twice and then I'm booted out. I can tell that the chroot is actually taking place because after I give the first password -- if I check /proc/pid#/root for that login process, it does list all the files I expect to see in that user's home dir. But I can't seem to get past the second password prompt. Restricted shell is ok but too easy to get out of, just run a different shell and bam, you're free. ;P
Re: chroot()ing a user's login
I would if they weren't all in the same dir Plus lots of other useful things like chmod. OTOH, anyone who did manage to hack an account with a restricted shell wouldn't have any business running chmod, so I suppose you could get away with just taking /bin out of his path. But then I imagine you might run into problems where the uid has to run shell scripts, then you're screwed again. :P hmmm. I guess then you would have to put a copy of a shell back in his path somewhere. At any rate I still haven't figured out why that account can't log in. :-\ On Mon, 13 Dec 1999, Stuart Ballard wrote: But with a restricted shell you can't run anything that isn't in your path, so just take all shells out of the path and bam, you're restricted again! :)
