similar to: FreeBSD Security Advisory FreeBSD-SA-03:17.procfs

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

I didn't get much (read: any) feedback from the freebsd-emulation list on this, so i'm passing it on myself. My original post can be found at: http://lists.freebsd.org/pipermail/freebsd-emulation/2003-August/000136.html A few days ago, i found myself in need of mounting a vmware image on my old 4.7-STABLE system. To do this, i needed linprocfs functioning properly, but this module

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:77 Security Advisory FreeBSD, Inc. Topic: Several vulnerabilities in procfs Category: core Module: procfs Announced: 2000-12-18

hi sirs, i try to install galeon2 for my machine but get an error messages that i really do not understand while making mozilla. that errors appear at the very beginning of a make command. i attache my uname, df both before and after make, and errors message with this mail. in wchich case that inodes are not sufficient ? and also how to get rid of this kind of error. thank you in advance for

Hi! I've updated the patch I've tested on 6.3 for 6.4 (only offsets differ), if anyone can test it I can file a PR so it hopefully :) can be committed: http://people.freebsd.org/~nox/linprocfs-6.4.patch (same patch for 6.3: http://people.freebsd.org/~nox/linprocfs-6.3.patch ) The original posting with the patch for RELENG_7 that I used is here:

After about a day and a half or so of uptime, I'm getting the aforementioned panic on the server ... better then having it hang solid, but right now I'm not sure if this is replacing it, or just one being triggered earlier then the other ... First scan through Google, I came across some posts talking about NMBCLUSTERS ... since its at the same settings as my other server (the default)

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Hi everybody, today I met the following problems on my freebsd box. I had a USB stick of opensolaris bootable USB image and tried to mount it on my fbsd box. The first time, when I tried to mount the usb device, my system freezed and then rebooted giving me one core in my dumpdev. When I tried to redo the mounting, the kernel informed me that the filesystem needed to be fsck'd before

I recently did a backport of a couple of networking bug fixes from s10x_u4_b6 to s10x_u3_b10. I patched just /platform/i86pc/kernel/unix and /platform/i86pc/kernel/amd64/unix in my existing u3 OS image and I''m seeing this dtrace problem when running any dtrace script: NODE hcb101 ~ $ ./tcpstat.sh dtrace: failed to compile script /dev/fd/10: "/usr/lib/dtrace/procfs.d", line

Author: peterte Repository: /hg/zfs-crypto/gate Revision: b681de1a640aeda1c2465325a301eec62c555cef Log message: 6324745 vmem memory leak in the procfs PAGEDATA subsystem. 6329403 hrm_init() cannot ever return -1 but in various places we check for that. 6330765 procfs pagedata can panic machine. Files: update: usr/src/uts/common/vm/hat_refmod.c

Hi there, from time to time my PC panics when I insert an empty DVD or CD-R. The kernel locks up instantly after the DVD writer's tray is closed. It seems burning the first DVD isn't critical but inserting the second one seems susceptible. I use k3b as software, which polls the hardware while the tray is open, maybe it's something with hald. Don't know, just use this. I

I know this has been brought up before but I''m receiving the error ... Process environment requires procfs(5) ... when trying to restart my cluster. I''ve narrowed it down to ''find_pid'' method in init.rb. I''m running a FreeBSD 6.2 server and mongrel_cluster version 1.0.5. The command that gives me the error is ... ps -ewwo pid,command ... but

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

Hello, I was wondering if it was possible to limit user access on /proc without having to use securelevels. For some reason chmod 751 /proc (or 750) does nothing. Is this possible on FreeBSD 4.9 ? Can't find anything about it in the manual pages. Just want to prevent lusers from running: for file in /proc/*/cmdline; do cat $file; echo; done Greetz, Jimmy Scott

I''m running the latest mongrel (1.0.1) and the latest mongrel_cluster (1.0.1.1) on FreeBSD 6.1. When I use capistrano to try to stop or restart my cluster I get this (partial) output: ps: Process environment requires procfs(5) And my Mongrel processes haven''t stopped. Any ideas? Thanks, Jamie

Hello, My server is experiencing occasional kernel panics when under moderate load. I'm attaching a crash dump and the dmesg output. I'm not sure how to read the kernel backtrace but it looks like the Intel NIC (em0) caused the problem. Occasionally, I used to get a "em0: watchdog timeout -- resetting" error message, but I never had a kernel panic. The problem started last

Just trying to understand if anything might be going on with this crash dump or just faulty hardware ? dmesg at the end ---Mike # gdb -k /kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type