From Fedora Project Wiki

< FWN‎ | Beats

m (1 revision(s))
 
(69 intermediate revisions by 4 users not shown)
Line 6: Line 6:
http://fedoraproject.org/wiki/Infrastructure
http://fedoraproject.org/wiki/Infrastructure


Contributing Writer:  HuzaifaSidhpurwala
Contributing Writer:  [[HuzaifaSidhpurwala|Huzaifa Sidhpurwala]]


=== proposed MM patch: improve rsync_acl query ===
=== Intrusion update ===
[[MikeMcGrath| Mike McGrath]] sent a link <ref>https://www.redhat.com/archives/fedora-announce-list/2009-March/msg00010.html</ref> to the list about the intrusion which was sent to the fedora-announce-list earlier.<ref>https://www.redhat.com/archives/fedora-infrastructure-list/2009-March/msg00277.html</ref>


Matt Domsch writes on fedora-infrastructure-list [1]
Mike said that he was waiting to discuss authentication mechanisms for the fedora-servers, Since passwords+ssh keys are not the most secure authentication mechanism. Also it seems that fedora does not have the budget for any RSA token like system for authentication.


mirrormanager has a query that lets the mirrors, and eventually, the master mirrors, get the Access Control List directly from the database.  The current query is poor in several ways: it's very slow as it uses python object walks, which results in hundreds of database hits instead of only one.  It doesn't let the user specify they want to limit by hosts on Internet2, or only public hosts. There is a patch which fixes this [2]
There was a lot of discussion on this thread, with various people proposing different authentication mechanisms which could be used.


[[Dennis Gilmore|DennisGilmore]] started a similar thread about Auth Mechanims<ref>https://www.redhat.com/archives/fedora-infrastructure-list/2009-March/msg00294.html</ref> on which he discussed using etoken or Yubikey for authentication.
It was a two factor authentication and therefore was more secure than passphrase or ssh keys.


[1]  https://www.redhat.com/archives/fedora-infrastructure-list/2008-April/msg00047.html
<references/>
 
[2]  http://admin.fedoraproject.org/mirrormanager/rsync_acl?internet2_only=1&public_only=1
 
=== Change (already) - steved ===
 
Mike McGrath writes for fedora-infrastructure-list [3]
 
One thing we'd been talking about before the freeze but just didn't get around to was giving steved (nfs expert) access to our nfs box where /mnt/koji lives as we still seem to be having nfslock issues (though they are less frequent now). Since everyone agreed to it, this was ultimately done.
 
 
[3]  https://www.redhat.com/archives/fedora-infrastructure-list/2008-April/msg00061.html
 
 
=== Change freeze request: Enforce website freeze in syncStatic.sh ===
 
Ricky Zhou writes for fedora-infrastructure-list [4]
 
Ricky said that he would like to update syncStatic.sh to enforce the website change freeze and submitted a patch for same.

Latest revision as of 04:36, 6 April 2009

Infrastructure

This section contains the discussion happening on the fedora-infrastructure-list

http://fedoraproject.org/wiki/Infrastructure

Contributing Writer: Huzaifa Sidhpurwala

Intrusion update

Mike McGrath sent a link [1] to the list about the intrusion which was sent to the fedora-announce-list earlier.[2]

Mike said that he was waiting to discuss authentication mechanisms for the fedora-servers, Since passwords+ssh keys are not the most secure authentication mechanism. Also it seems that fedora does not have the budget for any RSA token like system for authentication.

There was a lot of discussion on this thread, with various people proposing different authentication mechanisms which could be used.

DennisGilmore started a similar thread about Auth Mechanims[3] on which he discussed using etoken or Yubikey for authentication. It was a two factor authentication and therefore was more secure than passphrase or ssh keys.