Displaying 20 results from an estimated 200 matches similar to: "FreeBSD Security Advisory FreeBSD-SA-05:08.kmem [REVISED]"
2005 May 08
0
FreeBSD Security Advisory FreeBSD-SA-05:08.kmem [REVISED]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-05:08.kmem Security Advisory
The FreeBSD Project
Topic: Local kernel memory disclosure
Category: core
Module: sys
Announced: 2005-05-06
2005 May 05
1
FreeBSD Security Advisory FreeBSD-SA-05:08.kmem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-05:08.kmem Security Advisory
The FreeBSD Project
Topic: Local kernel memory disclosure
Category: core
Module: sys
Announced: 2005-05-06
2005 May 05
0
FreeBSD Security Advisory FreeBSD-SA-05:08.kmem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-05:08.kmem Security Advisory
The FreeBSD Project
Topic: Local kernel memory disclosure
Category: core
Module: sys
Announced: 2005-05-06
2008 Jul 24
0
cvs commit: src/contrib/pf/pfctl parse.y src/lib/libc/sys Symbol.map getsockopt.2 src/sbin/ipfw ipfw.8 ipfw2.c src/sys/conf NOTES options src/sys/contrib/ipfilter/netinet ip_fil_freebsd.c src/sys/contrib/pf/net pf.c pf_ioctl.c src/sys/kern init_sysent.c
This looks like a very cool feature addition to RELENG_7! Are there
any performance penalties that you know of with this built in ?
---Mike
At 09:13 PM 7/23/2008, Julian Elischer wrote:
>julian 2008-07-24 01:13:22 UTC
>
> FreeBSD src repository
>
> Modified files: (Branch: RELENG_7)
> contrib/pf/pfctl parse.y
> lib/libc/sys
2008 Sep 16
1
recent MFC of soreceive_dgram breaks kernels without INET6 option
Hello,
I just csup'd this morning and now I cannot build a kernel that does
not include INET6. I can send my KERNCONF, but it is sufficient to
create a kernel config with:
include GENERIC
nooption INET6
Here's the error during kernel compilation of a kernel config without
"options INET6" in the kernel config:
/usr/src/sys/netinet/udp_usrreq.c: In function
2004 Mar 02
0
FreeBSD Security Advisory FreeBSD-SA-04:04.tcp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-04:04.tcp Security Advisory
The FreeBSD Project
Topic: many out-of-sequence TCP packets denial-of-service
Category: core
Module: kernel
2004 Mar 02
7
FreeBSD Security Advisory FreeBSD-SA-04:04.tcp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-04:04.tcp Security Advisory
The FreeBSD Project
Topic: many out-of-sequence TCP packets denial-of-service
Category: core
Module: kernel
2004 Mar 02
1
Re: FreeBSD Security AdvisoryFreeBSD-SA-04:04.tcp
yes unless you use the version as of :> 2004-03-02 17:24:46
UTC (RELENG_5_2, 5.2.1-RELEASE-p1)
check it out with uname -a
if it does not say -p1
it affects you.
My guess, you are affected :)
cheers
--
Kind regards,
Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene
-----Oorspronkelijk bericht-----
Van:
2000 Oct 06
0
FreeBSD Security Advisory: FreeBSD-SA-00:52.tcp-iss
-----BEGIN PGP SIGNED MESSAGE-----
=============================================================================
FreeBSD-SA-00:52 Security Advisory
FreeBSD, Inc.
Topic: TCP uses weak initial sequence numbers
Category: core
Module: kernel
Announced: 2000-10-06
2004 Apr 20
1
[patch] Raw sockets in jails
Although RAW sockets can be used when specifying the source
address of packets (defeating one of the aspects of the jail)
some people may find it usefull to use utilities like ping(8)
or traceroute(8) from inside jails.
Enclosed is a patch I have written which gives you the option
of allowing prison-root to create raw sockets inside the prison,
so
2003 Apr 14
2
(OT) rfc1948 question
Hi, folks @ freebsd-security.
First, I am not sure if this is apropriate topic for that list, so
sorry, if it is not.
Some time ago I have read rfc1948 (protection from blind TCP spoofing)
and became interested in the way how it is implemented in FreeBSD.
After some googling (BTW if you like Google you might be interested in
this: http://register.spectator.ru/img/bart.gif ), I found this:
2003 Jun 11
1
nfs panic with umount -f
Hi Ian and others,
umount(8) -f does crash here on several just updated 4.8STABLE
boxes for nfs volumes. Server is an IRIX server. All clients are FreeBSD.
Here is a backtrace:
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0xc021f1c0 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0xc021f60d in panic (fmt=0xc03bd664 "from debugger")
at
2013 Sep 27
1
lock order reversal in 10-alpha2
After booting from a 10-alpha2 disk I am seeing "lock order reversal"
messages show up from time to time. Current logs have 35 entries.
The machine normally is running 9.1 from zfs root and I have setup a
separate disk (eSATA case connected through backplane port to onboard
SATA port) that I have installed 10-alpha amd64 onto a ufs partition to
test port building with. I started by
2006 Mar 17
1
acquiring duplicate lock of same type: "vnode interlock"
I think I've read somewhere about panic during early root mount, fsck
etc.. Perhaps this might be related:
Full dmesg: http://people.freebsd.org/~ariff/misc/dmesg.boot.amd64
[....]
acquiring duplicate lock of same type: "vnode interlock"
1st vnode interlock @ kern/vfs_vnops.c:791
2nd vnode interlock @ kern/vfs_subr.c:2018
KDB: stack backtrace:
witness_checkorder() at
2009 Apr 21
4
RELENG_7 crash
The box has a fairly heavy UDP load. Its RELENG_7 as of today and
took 3hrs for it to dump core.
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0637146
stack pointer = 0x28:0xe766eaac
frame pointer = 0x28:0xe766eb54
code segment
2013 Jul 07
1
Shutdown hangs on unmount of a gjournaled file system in 8-Stable
The problem occurs after an update of 8-stable from r248120 to r252111.
Sometimes shutdown hangs:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 done
All buffers synced.
>From the kernel
2013 Sep 12
1
9.2-RC1 panic at shutdown
Hello folks,
I have a panic at shutdown related to FUSE.
#0 doadump (textdump=<value optimized out>) at pcpu.h:234
234 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt full
#0 doadump (textdump=<value optimized out>) at pcpu.h:234
No locals.
#1 0xffffffff8090d9a6 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:449
_ep = (struct
2003 Jul 01
2
Okay, looks like I might have a *good* one here ... inode hang
neptune# ps -M vmcore.1 -N kernel.debug -axl | grep inode | wc -l
961
and I have a vmcore to work on here !! :)
(kgdb) proc 99643
(kgdb) bt
#0 mi_switch () at machine/globals.h:119
#1 0x8014a1f9 in tsleep (ident=0x8a4ef600, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479
#2 0x80141507 in acquire (lkp=0x8a4ef600, extflags=16777280,
2008 Mar 18
0
Freebsd/Xen: pcifront: IRQ resource allocation failed
Hi ,
I am testing pcifront on freebsd domU using following sound card
[ Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator]
Following sound driver is used for this sound card on Freebsd:
*snd_csa*-- Crystal Semiconductor CS461x/462x/4280 PCI bridge device driver
I am able to detect the card.
pci3: <PCI bus> on pcib3
csa0: <CS4280/CS4614/CS4622/CS4624/CS4630> mem
2009 Oct 29
1
Booting Error for /dev/kmem
Suddenly i found an error while booting, it says:
Fuck: can't open /dev/kmem for read/write (2)
So this is why, the Asterisk and Zaptel can not start.
Any Suggestions Please
Thanks a lot
Torintino
_________________________________________________________________
Windows Live: Make it easier for your friends to see what you?re up to on Facebook.