Re: Distributed SSH attack

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel O'Connor wrote: On Sat, 3 Oct 2009, krad wrote: simplest this to do is disable password auth, and use key based. Your logs are still full of crap though. I find sshguard works well, and I am fairly sure you couldn't spoof a valid TCP

[Fwd: HEADSUP: Call for FreeBSD Status Reports]

Hello guys, I would like to remind you about the FreeBSD Status Reports. The deadline is set to October 7th, and to date I have received only 5 reports, which is very little (considering the fact we are now covering almost 6 months). If you think you have anything to share with the community

(Ab)using rcng's features to keep rc.d-style services running should they fail.

Hi all, I realised that because portupgrade/portmaster don't always cleanly restart processes that have died due to being upgraded (mysqld, often!) that this was something I wanted to fix. However, I'd seen the daemontools and wasn't a fan - too much to configure with weird directories and

crashtar

Hi, http://trociny.googlecode.com/files/crashtar This simple script is useful for me and might be useful for other people too. The script creates tar archive that contains all files needed for debugging FreeBSD kernel crash (vmcore, kernel, loaded modules, sources that appear in backtrace). This

Make top display thread IDs

Hello, I was using top -H to display all the different threads on my system. I then wanted to use cpuset to pin a thread to a particular core, however, I couldn't find the thread ID. So I've hacked top to display thread IDs. Hopefully this patch is useful to something, and perhaps it should be

Re: (Ab)using rcng's features to keep rc.d-style services running should they fail.

Alex Trull wrote: Hi all, I realised that because portupgrade/portmaster don't always cleanly restart processes that have died due to being upgraded (mysqld, often!) that this was something I wanted to fix. I can't speak to portupgrade, however for portmaster there is no such facility

Re: Help debugging: Fatal kernel mode data abort: 'External Linefetch Abort (P)'

Hi Olivier, I have tried the patch and here are the boot results: i80321: BAR0 = 2004. BAR1 = 4004. i80219: BAR0 = 2000. BAR1 = 4000. i80219: I/O Processor, acting as PCI host i80321: SBDR = 0xa000 SBR0 = 0x0018 SBR1 = 0x0020

crashinfo: print the content of ddb capture budder

Hi, It would be nice if crashinfo(8) were also trying to output the content of ddb capture buffer. Something like in this patch: --- crashinfo.sh.orig 2009-10-05 08:26:26.0 +0300 +++ crashinfo.sh2009-10-05 08:43:56.0 +0300 @@ -304,3 +304,18 @@ echo kernel config echo