[Bug 219922] Internal "USR 3CP5610" modem not detected by "system-config-network"
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=219922
Bug Zapper <fedora-triage-list(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|rawhide |10
--- Comment #7 from Bug Zapper <fedora-triage-list(a)redhat.com> 2008-11-25 20:51:47 EDT ---
This bug appears to have been reported against 'rawhide' during the Fedora 10
development cycle.
Changing version to '10'.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--- Comment #8 from Joachim Frieben <jfrieben(a)hotmail.com> 2009-01-13 16:43:59 EDT ---
Hardware modem "USR 3CP5610" still not detected for current F10 w/updates but
usable after manual selection of device /dev/ttyS2 read off from
/var/log/dmesg. Relevant installed packages:
- kernel-2.6.28-1.fc10.x86_64
- kudzu-1.2.85-1.x86_64
- system-config-network-1.5.95-1.fc10.noarch
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 3 months
[Bug 213135] CVE-2008-2544 mounting proc readonly on a different mount point silently mounts it rw if the /proc mount is rw
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=213135
--- Comment #24 from Martin Cracauer <cracauer(a)cons.org> 2009-01-13 11:28:54 EDT ---
(In reply to comment #22)
> (In reply to comment #21)
> > 2) of course a read-write mounted /chroot/proc will instantly turn security
> > into a joke (as all processes, files and devices are accessible by anybody
> > becoming root in the chroot). But most of these applications, while requiring
> > a /proc, can live with a readonly /proc.
>
> If anybody in the chroot becomes root, she can escape chroot trivially without
> /proc mounted at all. Read-only vs. read-write /proc mount does not influence
> that much.
>
> > I strongly urge somebody who is running a recent Fedora to re-open this bug
> > report after confirming which behavior it is showing now.
>
> Has this been fixed, or is this test incorrect?
>
> # uname -r
> 2.6.27.9-159.fc10.x86_64
>
> # mkdir -p /chroot/proc
>
> # mount -o ro -t proc proc /chroot/proc/
>
> # cat /proc/mounts | grep '/proc proc'
> /proc /proc proc rw 0 0
> proc /chroot/proc proc ro 0 0
>
> # echo 1 > /proc/sys/net/ipv4/ip_forward
>
> # echo 1 > /chroot/proc/sys/net/ipv4/ip_forward
> bash: /chroot/proc/sys/net/ipv4/ip_forward: Read-only file system
This looks good.
I don't have FC anymore. My mainline 2.6.26.3 is still broken:
mount -o -ro -t proc proc /mnt/tmp
echo 1 > /mnt/tmp/sys/net/ipv4/ip_forward
# no complaints
Any idea whether this is a 2.6.27 or a Redhat/Fedora fix?
Thanks
Martin
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 3 months
[Bug 213135] CVE-2008-2544 mounting proc readonly on a different mount point silently mounts it rw if the /proc mount is rw
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=213135
--- Comment #22 from Tomas Hoger <thoger(a)redhat.com> 2009-01-13 03:03:00 EDT ---
(In reply to comment #21)
> 2) of course a read-write mounted /chroot/proc will instantly turn security
> into a joke (as all processes, files and devices are accessible by anybody
> becoming root in the chroot). But most of these applications, while requiring
> a /proc, can live with a readonly /proc.
If anybody in the chroot becomes root, she can escape chroot trivially without
/proc mounted at all. Read-only vs. read-write /proc mount does not influence
that much.
> I strongly urge somebody who is running a recent Fedora to re-open this bug
> report after confirming which behavior it is showing now.
Has this been fixed, or is this test incorrect?
# uname -r
2.6.27.9-159.fc10.x86_64
# mkdir -p /chroot/proc
# mount -o ro -t proc proc /chroot/proc/
# cat /proc/mounts | grep '/proc proc'
/proc /proc proc rw 0 0
proc /chroot/proc proc ro 0 0
# echo 1 > /proc/sys/net/ipv4/ip_forward
# echo 1 > /chroot/proc/sys/net/ipv4/ip_forward
bash: /chroot/proc/sys/net/ipv4/ip_forward: Read-only file system
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 3 months