similar to: [Discussion] User controls for PowerManagement

-----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 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

I'm trying to get veracity (http://www.rocksoft.com/veracity/), a tripwire replacement, working on FreeBSD 5.x. When I try and create a snapshot I get the following error for files sitting on my root partition: -- snip snip -- csh.logout E: Error opening binary (B) stream of file "/etc/csh.logout". (OS error message="File is on the procfs (/proc)

Hi! On BSD, mmap()ing files works on on-disk files but not on pseudo filesystems like kernfs or procfs. Therefore, attached patch mmap()s anonymous memory. Linux equivalents are sysfs and procfs to above BSD''s pseudo-filesystems. On Linux, mmap is implemented for sysfs but it is questionable to me how write operations work since (most) files in sysfs have static content. So this patch

Hi! What is the current status of support for PowerNow! and Speedstep? As I remember there were rumors, that those techniques were just supported for dom0, meaning that all the guests would run slow if dom0 idles. Is there already a solution for this implemented (in the unstable-tree), so that guests do also influence power-state? If so, does it also work with dualcore-cpus or is it better

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, At my work we have multiple freebsd machines running samba. Love it, things are working great. We have several windows 2000 servers that our engineers store their working drawings on. I need to create a mirror of this engineering windows 2000 machine to a freebsd machine running samba. The purpose of this is so that regular employees, welders whatever can just read the drawings on

Hello Folks, Just a status on upcoming advisories. FreeBSD-SA-03:15.openssh This is in final review and should be released today. Fixes for this issue entered the tree on September 24. I apologize for the delay in getting this one out. FreeBSD-SA-03:16.filedesc A reference counting bug was discovered that could lead to kernel memory disclosure or a system panic.

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

Renato, thanks for your elaborate walk-through of the issues with ARM boards. I'm trying to add some of this to the "How to Build on ARM" document and will submit a patch later on. I already ran into the problem of cores disappearing, but on Arch Linux (which uses a fairly recent kernel), the missing cores come back as soon as the load falls to zero. Unfortunately, my personal

'K, not sure how/what to debug here ... doing a grep of svr1.postgresql.org in /proc/*/status shows all the processes 'stuck' in inode ... /proc/38750/status:inetd 38750 2072 2072 2072 -1,-1 noflags 1055120147,191009 0,0 0,592 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org /proc/38752/status:inetd 38752 2072 2072 2072 -1,-1 noflags 1055120154,886433 0,0 0,637 inode 0 0

At Mon, 28 May 2018 18:23:42 -0700 CentOS mailing list <centos at centos.org> wrote: > > On 05/28/2018 03:25 PM, Robert Heller wrote: > > I tried to run efibootmgr, but it wants a model named efivars loaded, but > > there is no such module available. > > That's interesting.?? Can you post the command and output where you see that? > > Also, post the

On 14 November 2013 17:43, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Renato, thanks for your elaborate walk-through of the issues with ARM > boards. I'm trying to add some of this to the "How to Build on ARM" > document and will submit a patch later on. > Nice, thanks! That would be great! Unfortunately, my personal budget does not allow me more than a

-----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-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----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

-----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 am having trouble sending sysrq commands over USB serial, and I'm not sure what else to check. I have two identical machines, each with usb-to-serial adapters, joined by a null modem adapter. One runs an agetty, the other minicom. I can log in over the agetty as a user and it works as expected, until I try to send a sysrq. To send a break in minicom, I type [Ctrl]+[a] then [f]. Then I

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

Running freeBSD 6.1 After changing chkrootkit to the latest version V. 0.47 and compiling it then running it I get the following: ==================<SNIPPIT>================ Searching for anomalies in shell history files... nothing found Checking `asp'... not infected Checking `bindshell'... INFECTED (PORTS: 6667) Checking `lkm'... You have 131 process hidden for readdir