search for: paetzel

Please, note: http://secunia.com/advisories/23115/ A port maintainer CC'ed. -- Dixi. Sem.

----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 26 Oct 2012 09:55:22 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.3.0-RELEASE User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbi...

I have been playing around with 3 ath based FreeBSD boxes and seem to have got everything going via WPA and a common PSK for 802.11x auth. However, I want to have a bit more certainty about things working properly. What tools do people recommend for sniffing and checking a wireless network ? In terms of IDS, is there any way to see if people are trying to bruteforce the network ? I see

The raid card is an Adaptec 2100S. -----Original Message----- From: Josh Paetzel [mailto:josh at tcbug.org] Sent: Saturday, November 11, 2006 9:35 AM To: tclug-list at mn-linux.org; pjcrump at bitstream.net Subject: Re: [tclug-list] Drives Not Recognized on Dell Poweredge 1550 CentOs install On Saturday 11 November 2006 01:20, Phillip Crump wrote: > I have a new (used)Dell...

> John Freeman wrote: > >> Same problem on AMD64 build. I'm too lazy to attach full text, this >> system doesn't use bind and jail. > > What branch are you tracking? > > Doug > 6.2 STABLE (RELENG_6 latest cvs) amd64 -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:24.libarchive Security Advisory The FreeBSD Project Topic: Infinite loop in corrupt archives handling in libarchive(3) Category: core Module:

Hi everyone, Not sure if you've read http://www.win.tue.nl/hashclash/SoftIntCodeSign/ . should some kind of advisory be sent to advise people not to rely solely on MD5 checksums? Maybe an update to the man page is due ? : " MD5 has not yet (2001-09-03) been broken, but sufficient attacks have been made that its security is in some doubt. The attacks on MD5 are in the

Opensolaris this ain''t, but zfs-related nevertheless. ----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 13 Jul 2012 12:01:24 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.2.0-RC1 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/1...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:25.kmem Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in firewire(4) Category: core Module: sys_dev Announced:

Is for these UFS bugs in FreeBSD since 6.1 a fix uderway? See: http://projects.info-pull.com/mokb/ MOKB-08-11-2006,CVE-2006-5824, MOKB-03-11-2006,CVE-2006-5679 Regards, Oliver

Is for these UFS bugs in FreeBSD since 6.1 a fix uderway? See: http://projects.info-pull.com/mokb/ MOKB-08-11-2006,CVE-2006-5824, MOKB-03-11-2006,CVE-2006-5679 Regards, Oliver

...ns libgcc_s requires to find the correct unwind table. Open tasks: 1. Fix exception handling for EABI. __________________________________________________________________ FreeNAS URL: http://www.FreeNAS.org/ Contact: Alfred Perlstein <alfred at FreeBSD.org> Contact: Josh Paetzel <jpaetzel at FreeBSD.org> FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week of April, and should end up as the last FreeNAS release based on FreeBSD 8.X It's currently the only Free Open Source NAS product available with any form of ZFS encryption (provided by GEL...

Hi all, We have a server with a LSI 9240-4i controller configured in JBOD with 4 SATA disks. Running FreeBSD 9.1-Beta1: Relevant dmesg: FreeBSD 9.1-BETA1 #0: Thu Jul 12 09:38:51 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Xeon(R) CPU E31230 @ 3.20GHz (3200.09-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model =

Good Day! I think we have a serious problem. One of our old server running FreeBSD 4.9 have been compromised and is now connected to an ircd server.. 195.204.1.132.6667 ESTABLISHED However, we still haven't brought the server down in an attempt to track the intruder down. Right now we are clueless as to what we need to do.. Most of our servers are running legacy operating systems(old