From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 05:21, 27 January 2011 by Rashadul (talk | contribs)

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Rashadul Islam

Fedora Announcement News

The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]

OUTAGE: PHX2 Network outage - 2011-01-25 02:00 UTC

Stephen John Smoogen[1] on Thu Jan 20 21:36:58 UTC 2011 announced[2],

"There will be an outage starting at 2011-01-25 02:00 UTC, which will last approximately 3 hours.

To convert UTC to your local time, take a look at [3]

Howto or run:

date -d '2011-01-25 02:00 UTC'

Reason for outage:

We are moving from older netapp to newer one due to hardware limitations and aging hardware. Due to change in disk architectures and such, we will be having a total outage of Fedora services.

Affected Services:
  • BFO - [4]
  • Bodhi - [5]
  • Buildsystem - [6]
  • CVS / Source Control
  • Docs - [7]
  • Email system
  • Fedora Account System - [8]
  • Fedora Community -[9]
  • Fedora Hosted - [10]
  • Fedora People - [11]
  • Fedora Talk - [12]
  • Main Website - [13]
  • Mirror List - [14]
  • Mirror Manager - [15]
  • Package Database - [16]
  • Smolt - [17]
  • Spins - [18]
  • Start - [19]
  • Torrent - [20]
  • Translation Services -[21]
  • Wiki - [22]
Unaffected Services:

DNS - ns1.fedoraproject.org, ns2.fedoraproject.org

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

Ticket:

[23]"

Security incident on Fedora infrastructure on 23 Jan 2011

Jared K. Smith[1] on Tue Jan 25 00:14:23 UTC 2011 announced[2],

"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 (pkgs.fedoraproject.org, fedorapeople.org) 3. Audit SSH, FAS, Git, and Koji logs from the time of compromise to the present 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 any way
  • 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 compromise.

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 at 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 14 for IBM System z 64bit official release

Phil Knirsch[1] on Tue Jan 25 17:59:31 UTC 2011 announced[2],

"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 included.

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:

[3] [4]

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:

[5]

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:

[6]

Thanks go out to everyone involved in making this happen!"

Fedora Development News

The development list[1] is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above

rawhide update (2.91.6) of evolution-related packages is gtk3 only

Milan Crha[1] on Wed Jan 26 16:16:26 UTC 2011 announced[2],

"Evolution team drops support for gtk2 in 2.91.6 release of evolution-related packages (gtkhtml3, evolution-data-server and evolution) which might make trouble for dependent packages which are still gtk2. I expect there will follow gtk3 updates for them in the near future too, if not done already (this is mainly for packages using libedataserverui and gtkhtml3, the rest should be fine).

There are done soname bumps and api version bumps in above mentioned packages as well. The release will be done on Monday, when I plan to update rawhide too (+/- few days, if something will go wrong)."

Later Peter Robinson[3] on Wed Jan 26 18:15:33 UTC 2011 reply over the thread[4].

Fedora Events

Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (Dec 2010 - Feb 2011)

  • North America (NA)[1]
  • Central & South America (LATAM): [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Past Events

Archive of Past Fedora Events[1]

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.