[gentoo-user] Re: Blocking login attempts to sshd and vsftpd
In gmane.linux.gentoo.user, you wrote: On Sunday 15 November 2009 08:21:55 Walter Dnes wrote: On Sat, Nov 14, 2009 at 07:07:28PM -0500, Richard Marza wrote Thank you for the information, I did find that denyhost and fail2ban in threads but there were issues with it not working properly. Some users created custom scripts to get the job done correctly. Have you considered not allowing password-based logins at all for ssh? Use RSA keys instead. It's much easier, and much more secure. fail2ban and/or denyhosts is still very useful with key-only auth, even if only to get the spam out of messages and into the iptables logs I've hardened ssh by doing the following: * Only allow certain users to ssh * Not allowing passwd login, but only RSA * Switching ssh to a non-standard port This has dramatically reduced the amount of attacks my box gets. It's down to about 2 attacks per year, which is good enough for me. Another trick I learned about, but haven't implemented is changing the version string in sshd by patching the source. Ssh vunarability attacks actually check the version string, so if you change it to something unique, the scripts won't even try to get into your box.
[gentoo-user] Re: xdm doesn't restart on killed X
In gmane.linux.gentoo.user, you wrote: On Wednesday 11 November 2009 19:02:26 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Wednesday 11 November 2009 16:17:45 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Tuesday 10 November 2009 17:54:48 Doki Pen wrote: I've recently switched from gdm to xdm in an effort to reduce my distro size. The only problem I've run into is that when I kill my X session, xdm doesn't restart automatically. I have to switch to a vtty and type exec sudo /etc/init.d/xdm restart. I've read the man pages and googled but can't come up with a solution. Does anyone know if there is a way to fix this issue? When X exists, is xdm still running or has it died too? You can tell when restarting xdm if it gives errors about xdm not running when the stop phase of restart is run xdm is not running after I kill my xsession. It is running after I log in. I tested using ps -Af | grep -i xdm. Ok, so I reckon the init script dies because xdm dies when X exists. is there anything relevant in your messages log file, Xorg.0.log, ~/.xsession- errors and similar logs? From /var/log/Xorg.0.log.old: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x38) [0x812a180] Fatal server error: Caught signal 11. Server aborting That's a segfault so there's a serious bug. It's likely in X itself. Did you recently upgrade X and at the same time rebuild all it's app and all drivers - without exception? This has happened since I have switched to xdm. I've run revdep-rebuild and lafilefixer since my last X upgrade. Is there any other way to check for broken libs?
[gentoo-user] Re: xdm doesn't restart on killed X
In gmane.linux.gentoo.user, you wrote: On Thursday 12 November 2009 16:05:38 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Wednesday 11 November 2009 19:02:26 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Wednesday 11 November 2009 16:17:45 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Tuesday 10 November 2009 17:54:48 Doki Pen wrote: I've recently switched from gdm to xdm in an effort to reduce my distro size. The only problem I've run into is that when I kill my X session, xdm doesn't restart automatically. I have to switch to a vtty and type exec sudo /etc/init.d/xdm restart. I've read the man pages and googled but can't come up with a solution. Does anyone know if there is a way to fix this issue? When X exists, is xdm still running or has it died too? You can tell when restarting xdm if it gives errors about xdm not running when the stop phase of restart is run xdm is not running after I kill my xsession. It is running after I log in. I tested using ps -Af | grep -i xdm. Ok, so I reckon the init script dies because xdm dies when X exists. is there anything relevant in your messages log file, Xorg.0.log, ~/.xsession- errors and similar logs? From /var/log/Xorg.0.log.old: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x38) [0x812a180] Fatal server error: Caught signal 11. Server aborting That's a segfault so there's a serious bug. It's likely in X itself. Did you recently upgrade X and at the same time rebuild all it's app and all drivers - without exception? This has happened since I have switched to xdm. I've run revdep-rebuild and lafilefixer since my last X upgrade. Is there any other way to check for broken libs? Checking for broken libs is not going to fix a segfault. So what should I do? upgrade X? upgrade xdm?
[gentoo-user] Re: xdm doesn't restart on killed X
In gmane.linux.gentoo.user, you wrote: On Tuesday 10 November 2009 17:54:48 Doki Pen wrote: I've recently switched from gdm to xdm in an effort to reduce my distro size. The only problem I've run into is that when I kill my X session, xdm doesn't restart automatically. I have to switch to a vtty and type exec sudo /etc/init.d/xdm restart. I've read the man pages and googled but can't come up with a solution. Does anyone know if there is a way to fix this issue? When X exists, is xdm still running or has it died too? You can tell when restarting xdm if it gives errors about xdm not running when the stop phase of restart is run xdm is not running after I kill my xsession. It is running after I log in. I tested using ps -Af | grep -i xdm.
[gentoo-user] Re: xdm doesn't restart on killed X
In gmane.linux.gentoo.user, you wrote: On Wednesday 11 November 2009 16:17:45 doki_...@doki-pen.org wrote: In gmane.linux.gentoo.user, you wrote: On Tuesday 10 November 2009 17:54:48 Doki Pen wrote: I've recently switched from gdm to xdm in an effort to reduce my distro size. The only problem I've run into is that when I kill my X session, xdm doesn't restart automatically. I have to switch to a vtty and type exec sudo /etc/init.d/xdm restart. I've read the man pages and googled but can't come up with a solution. Does anyone know if there is a way to fix this issue? When X exists, is xdm still running or has it died too? You can tell when restarting xdm if it gives errors about xdm not running when the stop phase of restart is run xdm is not running after I kill my xsession. It is running after I log in. I tested using ps -Af | grep -i xdm. Ok, so I reckon the init script dies because xdm dies when X exists. is there anything relevant in your messages log file, Xorg.0.log, ~/.xsession- errors and similar logs? From /var/log/Xorg.0.log.old: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x38) [0x812a180] Fatal server error: Caught signal 11. Server aborting Nothing useful in .xession-errors
Re: [gentoo-user] Firefox 3 stability
Adam Carter wrote: I'm finding it unusable as it crashes often. How are you guys finding it? +2 on firefox3. Faster, doesn't slow down after long use. I really see the difference with javascript. The engine is much faster. Just try a js heavy page(like google apps). I haven't had any crashes. Only complaint is that flash blocker(or maybe flash itself) doesn't always work. I have to reload a couple of times to get youtube to work. Also, some plugins haven't been ported yet. I compiled it, and here are my use flags: dbus gnome ipv6 java linguas_en linguas_en_US mozdevelop startup-notification xulrunner -- gentoo-user@lists.gentoo.org mailing list
