Re: Infrastructure report, 2008-08-22 UTC 1200
by David Both
Any information on the attack vector?
Paul W. Frields wrote:
> Last week we discovered that some Fedora servers were illegally
> accessed. The intrusion into the servers was quickly discovered, and the
> servers were taken offline.
>
> Security specialists and administrators have been working since then to
> analyze the intrusion and the extent of the compromise as well as
> reinstall Fedora systems. We are using the requisite outages as an
> opportunity to do other upgrades for the sake of functionality as well
> as security. Work is ongoing, so please be patient. Anyone with
> pertinent information relating to this event is asked to contact
> fedora-legal(a)redhat.com.
>
> One of the compromised Fedora servers was a system used for signing
> Fedora packages. However, based on our efforts, we have high confidence
> that the intruder was not able to capture the passphrase used to secure
> the Fedora package signing key. Based on our review to date, the
> passphrase was not used during the time of the intrusion on the system
> and the passphrase is not stored on any of the Fedora servers.
>
> While there is no definitive evidence that the Fedora key has been
> compromised, because Fedora packages are distributed via multiple
> third-party mirrors and repositories, we have decided to convert to new
> Fedora signing keys. This may require affirmative steps from every
> Fedora system owner or administrator. We will widely and clearly
> communicate any such steps to help users when available.
>
> Among our other analyses, we have also done numerous checks of the
> Fedora package collection, and a significant amount of source
> verification as well, and have found no discrepancies that would
> indicate any loss of package integrity. These efforts have also not
> resulted in the discovery of additional security vulnerabilities in
> packages provided by Fedora.
>
> Our previous warnings against further package updates were based on an
> abundance of caution, out of respect for our users. This is also why we
> are proceeding with plans to change the Fedora package signing key. We
> have already started planning and implementing other additional
> safeguards for the future. At this time we are confident there is little
> risk to Fedora users who wish to install or upgrade signed Fedora
> packages.
>
> In connection with these events, Red Hat, Inc. detected an intrusion of
> certain of its computer systems and has issued a communication to Red
> Hat Enterprise Linux users which can be found at
> http://rhn.redhat.com/errata/RHSA-2008-0855.html. This communication
> states in part, "Last week Red Hat detected an intrusion on certain of
> its computer systems and took immediate action. While the investigation
> into the intrusion is on-going, our initial focus was to review and test
> the distribution channel we use with our customers, Red Hat Network
> (RHN) and its associated security measures. Based on these efforts, we
> remain highly confident that our systems and processes prevented the
> intrusion from compromising RHN or the content distributed via RHN and
> accordingly believe that customers who keep their systems updated using
> Red Hat Network are not at risk. We are issuing this alert primarily for
> those who may obtain Red Hat binary packages via channels other than
> those of official Red Hat subscribers."
>
> It is important to note that the effects of the intrusion on Fedora and
> Red Hat are *not* the same. Accordingly, the Fedora package signing key
> is not connected to, and is different from, the one used to sign Red Hat
> Enterprise Linux packages. Furthermore, the Fedora package signing key
> is also not connected to, and is different from, the one used to sign
> community Extra Packages for Enterprise Linux (EPEL) packages.
>
> We will continue to keep the Fedora community notified of any updates.
>
> Thank you again for your patience.
>
>
>
--
*********************************************************
"I'd put my money on the sun and solar energy. What a source of power! I hope we don't have to wait until oil and coal run out before we tackle that."
- Thomas Edison, in conversation with Henry Ford and Harvey Firestone, 1931
*********************************************************
David P. Both
15 years, 8 months
New windows open in background
by Matt Morgan
My 18 month-old was playing with the computer for a while, and now new
windows are opening in the background.
This is on Fedora 9. I googled this and searched the list, but can't find
any help. I'm not using the fancy new desktop stuff (compiz,
desktop-effects, whatever we call it). Any suggestions?
Thanks a lot,
Matt
15 years, 8 months
Linksys WRT54G2
by Rich Emberson
I run Fedora 9 (only, no windows or macs). I recently was given a Linksys
WRT54G2
Wireless-G broadband router with its installation CD (which according to the
terse instructions has a windows and mac modes - of course no Linux).
I want to use this as simply a wireless access point to my existing LAN. I
already have a router and DSL internet connection.
Anyone have any experience or links which can help me figure out how to use
this puppy?
Thanks
Richard
15 years, 8 months
How find my process id for my shell
by Dan Track
Hi
I'm logged in at the moment, how do I find my process id for the shell
I'm in, given that there are loads of other shells aswell. I'm using
bash?
Thanks
Dan
15 years, 8 months
cifs WinXP problem
by Michael D. Berger
Sorry to trouble you with what may be a Microsoft problem.
On my LAN, I replaced one of my Win2k boxes with a new
WinXP box. I use cifs to connect with MS boxes from an
FC7 box. Here is the main part of the start script in
init.d :
case $1 in
start)
mount -t cifs -o user=administrator%
xxx,noauto,suid,dir_mode=0700,file_mode=0700 //abcd30/base /mnt/base30
mount -t cifs -o user=administrator%
xxx,noauto,suid,dir_mode=0700,file_mode=0700 //abcd10/mike_local /mnt/
mike_local_10
abcd30 is a Win2k box.
abcd10 is the new WinXP box; mike_local is a share name on a directory.
abcd30 connects correctly; for abcd10 I get:
# smb start
mount error 5 = Input/output error
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
The man page says little of errors. I note that: ping works fine;
the new box and its shared directory are visible from other Win
boxes; the real passwords are the same on both boxes and have no
inappropriate characters. I tried shutting down iptables and
ZoneAlarm (with WAN disconnected, of course).
Thanks for your help.
Mike.
15 years, 8 months
hal-0.5.10-3.fc8 won't run
by Nataraj
After the latest updates to hal-0.5.10-3.fc8 and hal-info-20080607-2.fc8
hald won't start. I get errors shown below when I try to start it. This
is on a Fujitsu lifebook A6110 T5550 laptop.
Where can I download older updates between the release and the current
update? The update repository only has the latest update.
[root@alder ~]# hald --daemon=no
Runner started - allowed paths are '/usr/libexec:/usr/lib/hal/scripts:/usr/bin'
Run started hal-system-power-pm-is-supported (10000) (0)
! full path is '/usr/libexec/hal-system-power-pm-is-supported', program_dir is '/usr/libexec'
/usr/libexec/hal-system-power-pm-is-supported exited
(process:3609): GLib-CRITICAL **: g_hash_table_foreach_remove: assertion `hash_table != NULL' failed
Run started hald-probe-smbios (10000) (0)
! full path is '/usr/libexec/hald-probe-smbios', program_dir is '/usr/libexec'
(process:3609): GLib-CRITICAL **: g_hash_table_foreach_remove: assertion `hash_table != NULL' failed
/usr/libexec/hald-probe-smbios exited
Run started hald-addon-input (0) (0)
! full path is '/usr/libexec/hald-addon-input', program_dir is '/usr/libexec'
*** [DIE] device_info.c:rules_match_and_merge_device():1089 : Rule is NULL on jump
Run started hald-probe-input (10000) (0)
! full path is '/usr/libexec/hald-probe-input', program_dir is '/usr/libexec'
22:33:06.398 [D] addon-input.c:486: An error occured, exiting cleanly
[root@alder ~]# /usr/libexec/hald-addon-input exited
/usr/libexec/hald-probe-input exited
Thanks,
Nataraj
15 years, 8 months
More questions - OFF-LIST answers, please
by Anne Wilson
Thanks, everyone who has answered my original questions - and if you still
haven't, please do.
The team have asked if I can get more information, so that they can adequately
classify users and answers. Before I give you the questions, though, can I
say that my original post implied that I was only interested in KDE users.
That's not so. We're interested in the view of everyone who is using or has
used kickoff.
In order to make the answers more complete, we'd also like to know if your
wife/girlfriend/mother/grandmother/son/daughter has any experience of
kickoff, answering the same questions as before.
The additional information we'd like for each user is
What is your profession?
What is your technical proficiency level?
Which of the following age-bands do you fit into?
5-25 25-50 50+
Thank you once again for your help. The results are proving most interesting.
Anne
15 years, 8 months
Grub how to boot F8/F9 -
by Bob Goodwin
I recently installed F-9 using the Gnome LiveCD on a new hard drive.
When I opened the computer case there were only two SATA connectors on
the motherboard so I removed dev/sda and put the new drive in it's
place. The drive removed contained only the original XP which I don't
use and the /boot file. I chose the live cd to save bandwidth since I
am limited as to how much I can use via my satellite connection. I then
obtained what I want via yum.
After the installation finished I found that grub did not offer the F-8
Linux on the dev/sdb as an option. It just wasn't there. I had assumed
the installation would pick it up but didn't. Now a new /boot is on the
new drive.
I the bought an SATA card and installed it with the original drive
[/dev/sdc Windows XP and /boot] to it. I thought I might be able to
maniputlate the bios settings to control the boot situation at least
experimentally as a first step but no, when I go to bios-setup it only
shows two SATA drives with the third drive, the one on the added card,
as just being there with some identifying information but there's no way
I have found to boot from it short of swapping cables between the drives.
I can manipulate things from the command line well enough to copy files.
[mount /dev/mapper/VolGroup00-LogVol00 /mnt] makes the files available
under /mnt but ideally I would like to be able to boot from one or the
other, /dev/sda or /dev/sdc as it stands now. I've looked for
information on grub configuration but none of it is very clear to me.
What would help would be a how to with a few examples of typical grub
configuration files for a multi-boot system.
I guess I'm in over my head. Any suggestions pointing me in the right
direction will be appreciated.
Bob
15 years, 8 months
Re: Fedora 9 Freeze At Login
by vs
----- Original Message ----
> From: Kyle Lanigan <k.a.lanigan(a)gmail.com>
> To: fedora-list(a)redhat.com
> Sent: Sunday, August 31, 2008 11:10:38 AM
> Subject: Fedora 9 Freeze At Login
>
> So I've put in Fedora 9 just the other day, but it doesn't matter when
> I login into Fedora 9 after booting up into it, that everything
> freezes once the login screen goes away after entering my username and
> password. I'm not sure what I'm suppose to do to get this working.
Likely a device driver is causing this. The good news is that since it's so easy to reproduce you should be able to identify the driver, disable it and then start the usual hardware troubleshooting steps ( new driver, new firmware and so on ). I recommend booting up, then chvt 1 and wait for the crash to happen and see if the output on the screen shows the problem.
I had a similar problem with my wireless card connecting to WPA cards recently. I simply disable wireless at boot time in the BIOS to see if that was the problem. Once I confirmed this I updated firmware and drivers and the problem went away.
Good luck.
--Victor
> Kyle Lanigan
> k.a.lanigan(a)gmail.com
>
>
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
15 years, 8 months