FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 12-16-2010, 11:14 PM
 
Default koji using krb - having problems

Hello there.

I'm having some problems running koji using kerberos authentication.

I've verified that I have standard kerberos authentication from the
machine. I've followed the
http://fedoraproject.org/wiki/Koji/ServerHowTo howto document and I'm up
to the point where I'm trying to use the koji cli to create a user and I'm
getting:

The end of my koji-hub/hub.conf file looks like this:

AuthPrincipal host/bpbuild001.co0.nar.beatportcorp.net
AuthKeytab /etc/koji.keytab
ProxyPrincipals koji/bpbuild001.co0.nar.beatportcorp.net
HostPrincipalFormat compile/bpbuild001.co0.nar.beatportcorp.net

[root@bpbuild001 etc]# koji --authtype=kerberos add-user kojira
Kerberos authentication failed: No credentials cache found (-1765328189)
[root@bpbuild001 etc]# koji add-user kojira
Unable to log in, no authentication methods available

The document doesn't have any methods to verify/debug that I've gotten the
krb configs correct.. Is there a way to debug that I've done the krb
configs properly?

- Steve Webb

--
Steve Webb | System Administrator
Beatport | Music for DJ's
------------------------------------------
2399 Blake Street, Suite 170
Denver, Colorado USA 80205
tel: +1.720.932.9103
fax: +1.720.932.9104
noc: +1.303.565.2710
mobile: +1.303.564.4269
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 02:28 AM
Anthony Messina
 
Default koji using krb - having problems

On 12/16/2010 06:14 PM, steve.webb@beatport.com wrote:
> [root@bpbuild001 etc]# koji add-user kojira
> Unable to log in, no authentication methods available
>
> The document doesn't have any methods to verify/debug that I've gotten the
> krb configs correct.. Is there a way to debug that I've done the krb
> configs properly?

You are doing this under the root account. I'm guessing that your root
user might not be the koji administrative user you added during setup
and that you don't have kerberos credentials as that administrative user.

If the koji admin user you created had a username of 'steve' and
kerberos principal of steve@EXAMPLE.COM, then if you are logged in as
'steve' and have done a kinit steve@EXAMPLE.COM, you should then be able
to perform the tasks.

-A

--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 06:51 AM
Oliver Falk
 
Default koji using krb - having problems

He can get a valid ticket for steve@EXAMPLE.COM even if he logs in as root...

Steve, do you want us to take a look at your configs?
And can you provide a step-by-step example of what you have done?

-of

Anthony Messina <amessina@messinet.com> schrieb:

>On 12/16/2010 06:14 PM, steve.webb@beatport.com wrote:
>> [root@bpbuild001 etc]# koji add-user kojira
>> Unable to log in, no authentication methods available
>>
>> The document doesn't have any methods to verify/debug that I've gotten the
>> krb configs correct.. Is there a way to debug that I've done the krb
>> configs properly?
>
>You are doing this under the root account. I'm guessing that your root
>user might not be the koji administrative user you added during setup
>and that you don't have kerberos credentials as that administrative user.
>
>If the koji admin user you created had a username of 'steve' and
>kerberos principal of steve@EXAMPLE.COM, then if you are logged in as
>'steve' and have done a kinit steve@EXAMPLE.COM, you should then be able
>to perform the tasks.
>
>-A
>
>--
>Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
>8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
>
>
>--
>buildsys mailing list
>buildsys@lists.fedoraproject.org
>https://admin.fedoraproject.org/mailman/listinfo/buildsys
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 03:44 PM
 
Default koji using krb - having problems

Ok.

I got a krb ticket, gave myself a admin privs, then tried to add a user as
myself and I'm still getting "authentication failed".

koji=> insert into users (name, krb_principal, status, usertype) values ('swebb', 'swebb@AUTH.BEATPORTCORP.NET', 0, 0);
INSERT 0 1
koji=> select * from users;
id | name | password | status | usertype | krb_principal
----+-------+----------+--------+----------+------------------------------------------
1 | koji | | 0 | 0 | koji@bpbuild001.co0.nar.beatportcorp.net
2 | swebb | | 0 | 0 | swebb@AUTH.BEATPORTCORP.NET
(2 rows)

koji=> insert into user_perms (user_id, perm_id, creator_id) values (2, 1, 2);
INSERT 0 1
koji=> select * from user_perms;
user_id | perm_id | create_event | revoke_event | creator_id | revoker_id | active
---------+---------+--------------+--------------+------------+------------+--------
1 | 1 | 1 | | 1 | | t
2 | 1 | 2 | | 2 | | t
(2 rows)

[root@bpbuild001 etc]# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: swebb@AUTH.BEATPORTCORP.NET

Valid starting Expires Service principal
12/17/10 09:39:56 12/17/10 21:37:58 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET
[root@bpbuild001 etc]# koji add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)

Is there still something missing?

- Steve Webb

On Thu, 16 Dec 2010, Anthony Messina wrote:

> On 12/16/2010 06:14 PM, steve.webb@beatport.com wrote:
>> [root@bpbuild001 etc]# koji add-user kojira
>> Unable to log in, no authentication methods available
>>
>> The document doesn't have any methods to verify/debug that I've gotten the
>> krb configs correct.. Is there a way to debug that I've done the krb
>> configs properly?
>
> You are doing this under the root account. I'm guessing that your root
> user might not be the koji administrative user you added during setup
> and that you don't have kerberos credentials as that administrative user.
>
> If the koji admin user you created had a username of 'steve' and
> kerberos principal of steve@EXAMPLE.COM, then if you are logged in as
> 'steve' and have done a kinit steve@EXAMPLE.COM, you should then be able
> to perform the tasks.
>
> -A
>
>

--
Steve Webb | System Administrator
Beatport | Music for DJ's
------------------------------------------
2399 Blake Street, Suite 170
Denver, Colorado USA 80205
tel: +1.720.932.9103
fax: +1.720.932.9104
noc: +1.303.565.2710
mobile: +1.303.564.4269
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 04:02 PM
 
Default koji using krb - having problems

> Steve, do you want us to take a look at your configs?
> And can you provide a step-by-step example of what you have done?

Sure.

I went through the http://fedoraproject.org/wiki/Koji/ServerHowTo document
and follow the kerberos installation instructions.

* I set up a DNS record as instructed (_kerberos._udp IN SRV 10 100 88 ...)
* U added the principals into IPA but used:
host/kojihub@bpbuild001.co0.beatportcorp.net
not
host/kojihub@AUTH.BEATPORCORP.NET
(could this be an issue?)

All krb principals added to IPA for koji:

# ipa-addservice host/bpbuild001.co0.nar.beatportcorp.net
# ipa-addservice HTTP/bpbuild001.co0.nar.beatportcorp.net
# ipa-addservice koji/bpbuild001.co0.nar.beatportcorp.net
# ipa-addservice compile/bpbuild001.co0.nar.beatportcorp.net

* I set up psql - seems to be working properly.
* I can get a normal krb ticket as myself on the koji server just fine
* I inserted the users into psql as instructed on the howto
* Some config files:

/etc/koji-hub/hub.conf:
[hub]
DBName = koji
DBUser = koji
DBHost = bpbuild001.co0
KojiDir = /data/koji
LoginCreatesUser = On
KojiWebURL = http://bpbuild001.co0.nar.beatportcorp.net/koji
NotifyOnSuccess = True
AuthPrincipal host/bpbuild001.co0.nar.beatportcorp.net
AuthKeytab /etc/koji.keytab
ProxyPrincipals koji/bpbuild001.co0.nar.beatportcorp.net
HostPrincipalFormat compile/bpbuild001.co0.nar.beatportcorp.net

Anything else you need from me to help debug?

- Steve Webb

--
Steve Webb | System Administrator
Beatport | Music for DJ's
------------------------------------------
2399 Blake Street, Suite 170
Denver, Colorado USA 80205
tel: +1.720.932.9103
fax: +1.720.932.9104
noc: +1.303.565.2710
mobile: +1.303.564.4269
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 04:20 PM
Mike Bonnet
 
Default koji using krb - having problems

On 12/17/2010 11:44 AM, steve.webb@beatport.com wrote:
> Ok.
>
> I got a krb ticket, gave myself a admin privs, then tried to add a user as
> myself and I'm still getting "authentication failed".
>
> koji=> insert into users (name, krb_principal, status, usertype) values ('swebb', 'swebb@AUTH.BEATPORTCORP.NET', 0, 0);
> INSERT 0 1
> koji=> select * from users;
> id | name | password | status | usertype | krb_principal
> ----+-------+----------+--------+----------+------------------------------------------
> 1 | koji | | 0 | 0 | koji@bpbuild001.co0.nar.beatportcorp.net
> 2 | swebb | | 0 | 0 | swebb@AUTH.BEATPORTCORP.NET
> (2 rows)
>
> koji=> insert into user_perms (user_id, perm_id, creator_id) values (2, 1, 2);
> INSERT 0 1
> koji=> select * from user_perms;
> user_id | perm_id | create_event | revoke_event | creator_id | revoker_id | active
> ---------+---------+--------------+--------------+------------+------------+--------
> 1 | 1 | 1 | | 1 | | t
> 2 | 1 | 2 | | 2 | | t
> (2 rows)
>
> [root@bpbuild001 etc]# klist
> Ticket cache: FILE:/tmp/krb5cc_0
> Default principal: swebb@AUTH.BEATPORTCORP.NET
>
> Valid starting Expires Service principal
> 12/17/10 09:39:56 12/17/10 21:37:58 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET
> [root@bpbuild001 etc]# koji add-user kojira
> Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
>
> Is there still something missing?

The koji cli expects the service principal of the hub to be host/<server
name>@<last 2 tokens of the server name>. So in your case it is trying
to lookup a service principal in the BEATPORTCORP.NET domain, rather
than AUTH.BEATPORTCORP.NET. Koji should probably be determining the
domain from the client principal, rather than the DNS name. In the
meantime, you could patch __init__.py:_serverPrincipal() to return the
correct value.

> - Steve Webb
>
> On Thu, 16 Dec 2010, Anthony Messina wrote:
>
>> On 12/16/2010 06:14 PM, steve.webb@beatport.com wrote:
>>> [root@bpbuild001 etc]# koji add-user kojira
>>> Unable to log in, no authentication methods available
>>>
>>> The document doesn't have any methods to verify/debug that I've gotten the
>>> krb configs correct.. Is there a way to debug that I've done the krb
>>> configs properly?
>>
>> You are doing this under the root account. I'm guessing that your root
>> user might not be the koji administrative user you added during setup
>> and that you don't have kerberos credentials as that administrative user.
>>
>> If the koji admin user you created had a username of 'steve' and
>> kerberos principal of steve@EXAMPLE.COM, then if you are logged in as
>> 'steve' and have done a kinit steve@EXAMPLE.COM, you should then be able
>> to perform the tasks.
>>
>> -A
>>
>>
>

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 04:35 PM
 
Default koji using krb - having problems

> The koji cli expects the service principal of the hub to be host/<server
> name>@<last 2 tokens of the server name>. So in your case it is trying
> to lookup a service principal in the BEATPORTCORP.NET domain, rather
> than AUTH.BEATPORTCORP.NET. Koji should probably be determining the
> domain from the client principal, rather than the DNS name. In the
> meantime, you could patch __init__.py:_serverPrincipal() to return the
> correct value.

I just changed it to accept 3 parts to the server name by changing the 2s
to 3s in /usr/lib/python2.7/site-packages/koji/__init__.py

def _serverPrincipal(self):
"""Get the Kerberos principal of the server we're connecting
to, based on baseurl. Assume the last two components of the
server name are the Kerberos realm."""
servername = urlparse.urlparse(self.baseurl)[1]
portspec = servername.find(':')
if portspec != -1:
servername = servername[ortspec]

parts = servername.split('.')
if len(parts) < 3:
domain = servername.upper()
else:
domain = '.'.join(parts[-3:]).upper()

return 'host/%s@%s' % (servername, domain)


Still getting authentication failure:

[root@bpbuild001 ~]# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: swebb@AUTH.BEATPORTCORP.NET

Valid starting Expires Service principal
12/17/10 09:39:56 12/17/10 21:37:58 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET

[root@bpbuild001 ~]# koji add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)


--
Steve Webb | System Administrator
Beatport | Music for DJ's
------------------------------------------
2399 Blake Street, Suite 170
Denver, Colorado USA 80205
tel: +1.720.932.9103
fax: +1.720.932.9104
noc: +1.303.565.2710
mobile: +1.303.564.4269
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 05:06 PM
Mike Bonnet
 
Default koji using krb - having problems

On 12/17/2010 12:35 PM, steve.webb@beatport.com wrote:
>> The koji cli expects the service principal of the hub to be host/<server
>> name>@<last 2 tokens of the server name>. So in your case it is trying
>> to lookup a service principal in the BEATPORTCORP.NET domain, rather
>> than AUTH.BEATPORTCORP.NET. Koji should probably be determining the
>> domain from the client principal, rather than the DNS name. In the
>> meantime, you could patch __init__.py:_serverPrincipal() to return the
>> correct value.
>
> I just changed it to accept 3 parts to the server name by changing the 2s
> to 3s in /usr/lib/python2.7/site-packages/koji/__init__.py
>
> def _serverPrincipal(self):
> """Get the Kerberos principal of the server we're connecting
> to, based on baseurl. Assume the last two components of the
> server name are the Kerberos realm."""
> servername = urlparse.urlparse(self.baseurl)[1]
> portspec = servername.find(':')
> if portspec != -1:
> servername = servername[ortspec]
>
> parts = servername.split('.')
> if len(parts) < 3:
> domain = servername.upper()
> else:
> domain = '.'.join(parts[-3:]).upper()
>
> return 'host/%s@%s' % (servername, domain)
>
>
> Still getting authentication failure:
>
> [root@bpbuild001 ~]# klist
> Ticket cache: FILE:/tmp/krb5cc_0
> Default principal: swebb@AUTH.BEATPORTCORP.NET
>
> Valid starting Expires Service principal
> 12/17/10 09:39:56 12/17/10 21:37:58 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET
>
> [root@bpbuild001 ~]# koji add-user kojira
> Kerberos authentication failed: Server not found in Kerberos database (-1765328377)

Assuming your hub is running on bpbuild001.co0.nar.beatportcorp.net, your /etc/koji-hub/hub.conf should have:

AuthPrincipal = host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET

and AuthKeytab should be pointing at a keytab for that principal.

Yes, this could be a lot more flexible.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 08:00 PM
Anthony Messina
 
Default koji using krb - having problems

On 12/17/2010 01:51 AM, Oliver Falk wrote:
> He can get a valid ticket for steve@EXAMPLE.COM even if he logs in as root...

of course. it's just an easy thing to forget. glad you guys found the
real solution.

--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 08:51 PM
 
Default koji using krb - having problems

Ok, I'm still not getting access to krb, but I feel that I'm getting
close. (Thanks for all of your help already, BTW)

[root@bpbuild001 ~]# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: swebb@AUTH.BEATPORTCORP.NET

Valid starting Expires Service principal
12/17/10 14:27:51 12/18/10 02:27:09 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET

[root@bpbuild001 ~]# su - koji
[koji@bpbuild001 ~]$ psql
psql (8.4.5)
Type "help" for help.

koji=> select * from user_perms;
user_id | perm_id | create_event | revoke_event | creator_id | revoker_id | active
---------+---------+--------------+--------------+------------+------------+--------
1 | 1 | 1 | | 1 | | t
2 | 1 | 2 | | 2 | | t
(2 rows)

koji=> select * from users;
id | name | password | status | usertype | krb_principal
----+-------+----------+--------+----------+------------------------------------------
1 | koji | | 0 | 0 | koji@bpbuild001.co0.nar.beatportcorp.net
2 | swebb | | 0 | 0 | swebb@AUTH.BEATPORTCORP.NET
(2 rows)

koji=>
[koji@bpbuild001 ~]$ logout
[root@bpbuild001 ~]# koji --keytab=/etc/krb5.keytab --authtype=kerberos add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
[root@bpbuild001 ~]# koji --keytab=/etc/krb5.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net --authtype=kerberos add-user kojira
Kerberos authentication failed: Decrypt integrity check failed (-1765328353)
[root@bpbuild001 ~]# koji --keytab=/etc/krb5.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET --authtype=kerberos add-user kojira
Kerberos authentication failed: Decrypt integrity check failed (-1765328353)
[root@bpbuild001 ~]# koji --keytab=/etc/koji2.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET --authtype=kerberos add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
[root@bpbuild001 ~]# koji --keytab=/etc/koji2.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net --authtype=kerberos add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
[root@bpbuild001 ~]# koji --keytab=/etc/koji2.keytab --authtype=kerberos add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
[root@bpbuild001 ~]# koji --keytab=/etc/koji.keytab --authtype=kerberos add-user kojira
Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
[root@bpbuild001 ~]# koji --keytab=/etc/koji.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net --authtype=kerberos add-user kojira
Kerberos authentication failed: Key table entry not found (-1765328203)
[root@bpbuild001 ~]# koji --keytab=/etc/koji.keytab --principal=host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET --authtype=kerberos add-user kojira
Kerberos authentication failed: Key table entry not found (-1765328203)

My keytabs that I've been trying:

/etc/krb5.keytab: host/bpbuild001.co0.nar.beatportcorp.net
/etc/koji.keytab: koji/bpbuild001.co0.nar.beatportcorp.net
/etc/koji2.keytab: host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET

I've tried many combinations but none of them seem to be working. The
most common errors are (in order of # of occurrences):

Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
Kerberos authentication failed: Decrypt integrity check failed (-1765328353)
Kerberos authentication failed: Key table entry not found (-1765328203)

I'm very good with kerberos, but I'm hoping that this may help us get
close to getting kerberos working.

Is there a way to turn on logging for the kerberos authentication stuff
somewhere? Using --debug doesn't seem to provide any additional
information.

My /etc/koji-hub/hub.conf now:

[snip]
AuthPrincipal = host/bpbuild001.co0.nar.beatportcorp.net
AuthKeytab = /etc/krb5.keytab
ProxyPrincipals = koji/bpbuild001.co0.nar.beatportcorp.net
HostPrincipalFormat = compile/bpbuild001.co0.nar.beatportcorp.net
[snip]

Thanks again.

- Steve

On Fri, 17 Dec 2010, Mike Bonnet wrote:

> On 12/17/2010 12:35 PM, steve.webb@beatport.com wrote:
>>> The koji cli expects the service principal of the hub to be host/<server
>>> name>@<last 2 tokens of the server name>. So in your case it is trying
>>> to lookup a service principal in the BEATPORTCORP.NET domain, rather
>>> than AUTH.BEATPORTCORP.NET. Koji should probably be determining the
>>> domain from the client principal, rather than the DNS name. In the
>>> meantime, you could patch __init__.py:_serverPrincipal() to return the
>>> correct value.
>>
>> I just changed it to accept 3 parts to the server name by changing the 2s
>> to 3s in /usr/lib/python2.7/site-packages/koji/__init__.py
>>
>> def _serverPrincipal(self):
>> """Get the Kerberos principal of the server we're connecting
>> to, based on baseurl. Assume the last two components of the
>> server name are the Kerberos realm."""
>> servername = urlparse.urlparse(self.baseurl)[1]
>> portspec = servername.find(':')
>> if portspec != -1:
>> servername = servername[ortspec]
>>
>> parts = servername.split('.')
>> if len(parts) < 3:
>> domain = servername.upper()
>> else:
>> domain = '.'.join(parts[-3:]).upper()
>>
>> return 'host/%s@%s' % (servername, domain)
>>
>>
>> Still getting authentication failure:
>>
>> [root@bpbuild001 ~]# klist
>> Ticket cache: FILE:/tmp/krb5cc_0
>> Default principal: swebb@AUTH.BEATPORTCORP.NET
>>
>> Valid starting Expires Service principal
>> 12/17/10 09:39:56 12/17/10 21:37:58 krbtgt/AUTH.BEATPORTCORP.NET@AUTH.BEATPORTCORP.NET
>>
>> [root@bpbuild001 ~]# koji add-user kojira
>> Kerberos authentication failed: Server not found in Kerberos database (-1765328377)
>
> Assuming your hub is running on bpbuild001.co0.nar.beatportcorp.net, your /etc/koji-hub/hub.conf should have:
>
> AuthPrincipal = host/bpbuild001.co0.nar.beatportcorp.net@AUTH.BEATPORTC ORP.NET
>
> and AuthKeytab should be pointing at a keytab for that principal.
>
> Yes, this could be a lot more flexible.
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>

--
Steve Webb | System Administrator
Beatport | Music for DJ's
------------------------------------------
2399 Blake Street, Suite 170
Denver, Colorado USA 80205
tel: +1.720.932.9103
fax: +1.720.932.9104
noc: +1.303.565.2710
mobile: +1.303.564.4269
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 11:11 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org