On Sat, Jan 29, 2011 at 1:10 AM, Clint Savage <herlo1(a)gmail.com> wrote:
> If you are coming to FUDCon Tempe and have never been to the ASU
> campus, we don’t want you to get lost. Let the FUDCon tour guides help
> you out on your way over to the barcamp pitches tomorrow morning.
> Every 10 minutes, starting at 7:45am, meet in the lobby of the
> Courtyard Marriott. You will be directed on a walking tour as we head
> toward the Center for Design North (CDN), also known as the
> Architecture and Environmental Design Building (AED).
> On the tour, you will see the following items:
> * A short tour of Mill Avenue, with restaurants and pubs
> * The Brickyard Artisan Court (where the Barcamp sessions will be held)
> * The Center for Design North (where the Barcamp pitches will be held)
> In addition to all this, you’ll be on time to the barcamp pitches!
> But don’t miss out, the last tour will begin at 8:45 so we can all get
> there before 9am.
> If you don’t get the tour, you can still make it on your own. Here’s
> a map with information to make it simple and straightforward. It’s
> a google map and works well by searching for the url right in your
> maps program on a smart phone.
> See you all tomorrow!
> 1 - http://ur1.ca/31gne
-----BEGIN PGP SIGNED MESSAGE-----
On behalf of the event planning team and FPL Jared Smith, I wanted to
point out some helpful information for people traveling to FUDCon
Tempe for this weekend's event. This information is all available on
our wiki as well.
WIKI PAGE: https://fedoraproject.org/wiki/FUDCon:Tempe_2011
PACKING LIST: Organizers put together a helpful list of things you'll
likely want to bring with you:
HOTELS: Here are the addresses for both hotels:
Courtyard Tempe Downtown: 601 South Ash Avenue, Tempe, AZ 85281
+1 (480) 966-2800
Four Points Sheraton Tempe: 1333 Rural Rd.. Tempe, AZ 85281
+1 (480) 968-3451
HOSPITALITY SUITE: The suite will open at 5:00pm on Friday evening,
and has MOVED to Meeting Room *B* at the Courtyard Tempe Downtown.
Opensource.com is celebrating its one-year anniversary and will be on
hand to celebrate with us. There will be pizza, beverages, cake, good
conversation, hacking, and board-gaming.
PACKETS: You'll be able to pick up a FUDCon packet with your badge
either Friday night or at registration on Saturday. Note the packets
were printed a few weeks earlier, so there will be an errata sheet
including information that has changed since print time. The wiki
continues to include the latest available information.
OPENING SESSION: The opening session has MOVED to Center for Design
North (CDN) room 60 (a larger auditorium). We will start PROMPTLY at
9:00am. The CDN building is approximately a 10-15 minute walk from
the Courtyard hotel. The opening session will include the BarCamp
setup and the FPL address. The first session begins at 11:00am in the
BYAC building, which is a short walk from CDN.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
It's been a long time since we last had an official release of IBM
System z on Fedora...
A really long time...
A really, really long time...
In fact and to be precise, it's been 134,265,600 seconds or 2,237,760
minutes or 37,296 hours or 1554 days since Fedora 6 was released on
October 24th 2006 which was the last release where IBM System z was
But today, today changes all this.
As today, the Fedora IBM System z (s390x) Secondary Arch team proudly
presents the Fedora 14 for IBM System z 64bit official release!
And without further ado, here the links to the actual release:
and obviously on all mirrors that mirror the secondary arch content.
The first directory contains the normal installation trees as well as 1
DVD ISO and 5 CD ISOs with the complete release.
Everything as usual contains, well, everything. :)
We have collected a couple of example config files, kickstart examples
and a nice README here:
but beware that currently the images found there are still outdated,
we're working on fixing that over the next weeks.
Additional information about know issues, the current progress and state
for future release, where and how the team can be reached and just
anything else IBM System z on Fedora related can be found here:
Thanks go out to everyone involved in making this happen!
Philipp Knirsch | Tel.: +49-711-96437-470
Supervisor Core Services | Fax.: +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch <pknirsch(a)redhat.com>
Hauptstaetterstr. 58 | Web: http://www.redhat.com/
D-70178 Stuttgart, Germany
Motd: You're only jealous cos the little penguins are talking to me.
Summary: Fedora infrastructure intrusion but no impact on product integrity
On January 22, 2011 a Fedora contributor received an email from the Fedora
Accounts System indicating that his account details had been changed. He
contacted the Fedora Infrastructure Team indicating that he had received
the email, but had not made changes to his FAS account. The Infrastructure
Team immediately began investigating, and confirmed that the account had
indeed been compromised.
At this time, the Infrastructure Team has evidence that indicates the account
credentials were compromised externally, and that the Fedora Infrastructure was
not subject to any code vulnerability or exploit.
The account in question was not a member of any sysadmin or Release Engineering
groups. The following is a complete list of privileges on the account:
* SSH to fedorapeople.org (user permissions are very limited on this machine).
* Push access to packages in the Fedora SCM.
* Ability to perform builds and make updates to Fedora packages.
The Infrastructure Team took the following actions after being
notified of the issue:
1. Lock down access to the compromised account
2. Take filesystem snapshots of all systems the account had access to
3. Audit SSH, FAS, Git, and Koji logs from the time of compromise to the
Here, we found that the attacker did:
* Change the account's SSH key in FAS
* Login to fedorapeople.org
The attacker did not:
* Push any changes to the Fedora SCM or access pkgs.fedoraproject.org in
* Generate a koji cert or perform any builds
* Push any package updates
Based on the results of our investigation so far, we do not believe that any
Fedora packages or other Fedora contributor accounts were affected by this
While the user in question had the ability to commit to Fedora SCM, the
Infrastructure Team does not believe that the compromised account was used to
do this, or cause any builds or updates in the Fedora build system. The
Infrastructure Team believes that Fedora users are in no way threatened by this
security breach and we have found no evidence that the compromise extended
beyond this single account.
As always, Fedora packagers are recommended to regularly review commits to
their packages and report any suspicious activity that they notice.
Fedora contributors are strongly encouraged to choose a strong FAS password.
Contributors should *NOT* use their FAS password on any other websites or
user accounts. If you receive an email from FAS notifying you of changes to
your account that you did not make, please contact the Fedora Infrastructure
team immediately via admin(a)fedoraproject.org.
We are still performing a more in-depth investigation and security audit and we
will post again if there are any material changes to our understanding.
Fedora Project Leader
The Extra Packages for Enterprise Linux (EPEL) project is happy to
announce the release of EPEL 6 today!
EPEL 6 is a collection of add-on packages available for Red Hat
Enterprise Linux (RHEL) 6 and other compatible systems, maintained by
the community under the umbrella of the Fedora Project. EPEL 6 is
designed to supplement RHEL 6 by providing additional functionality
and does not replace any RHEL 6 packages. As a community project,
EPEL is maintained and supported by volunteers via Bugzilla and
mailing lists. EPEL is not commercially supported by Red Hat, Inc.
Included are over 2500 source packages that build into over 5600
binary packages. We are always seeking volunteers eager and willing
to help maintain new packages. Refer to the URL below to join us!
* rt3 - The Request Tracker Bug and Ticket tracking system, as well as
it's 90 perl packages dependencies.
* trac - Project management system, along with many plugins.
* haproxy, varnish and lighttpd proxies and web servers.
* BackupPC, rdiff-backup and other backup clients.
* A large stack of Ruby packages.
* Spamassassin plugins, clamav and other mail server and filtering
* rkhunter and chkrootkit security scanners.
* collectd, munin, nagios and cacti monitoring solutions.
* Over 600 perl packages.
* And many more...
To use EPEL 6:
To Join us, or for more information on the EPEL project: