Bug 7481 - Request for CVS account for ldtp group
Summary: Request for CVS account for ldtp group
Status: RESOLVED DUPLICATE of bug 11327
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: New Accounts (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: fd.o Admin Massive
QA Contact:
URL: http://ldtp.freedesktop.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-10 09:24 UTC by Harishankaran
Modified: 2007-06-21 11:15 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
My Gpg key (1.66 KB, application/octet-stream)
2006-07-10 09:27 UTC, Harishankaran
Details
my ssh pub key (229 bytes, application/octet-stream)
2006-07-10 09:33 UTC, Harishankaran
Details
gpg key (3.20 KB, text/plain)
2006-07-25 13:55 UTC, Harishankaran
Details
my ssh-key (229 bytes, text/plain)
2006-07-25 13:56 UTC, Harishankaran
Details
New gpg key (1.65 KB, text/plain)
2006-07-28 04:20 UTC, Harishankaran
Details
My PGP PUBLIC KEY (1.65 KB, text/plain)
2007-06-18 23:48 UTC, Harishankaran
Details

Description Harishankaran 2006-07-10 09:24:01 UTC
Real Name: K.Harishankaran
E-Mail id: sp2hari at gmail.com
preffered account name: sp2hari
Comment 1 Harishankaran 2006-07-10 09:27:52 UTC
Created attachment 6175 [details]
My Gpg key

Have attached my gpg key
Comment 2 Harishankaran 2006-07-10 09:33:51 UTC
Created attachment 6176 [details]
my ssh pub key

My ssh public key
Comment 3 Nagappan Alagappan 2006-07-10 10:07:03 UTC
Administrator, Please give CVS access to sp2hari.

Thanks
Nagappan
Comment 4 Harishankaran 2006-07-25 13:55:11 UTC
Created attachment 6336 [details]
gpg key
Comment 5 Harishankaran 2006-07-25 13:56:08 UTC
Created attachment 6337 [details]
my ssh-key
Comment 6 Harishankaran 2006-07-25 14:04:07 UTC
have no idea why it is taking such a long time to create an account for me 

If something is wrong with my gpg keys and ssh keys i had created new ones and
uploaded them . 

If there is any problem with them , please mention it and do try to give the
accounts asap .

Thanks in advance 
Comment 7 Daniel Stone 2006-07-26 03:54:54 UTC
you have two keys there.  which one do you want to use?
Comment 8 Harishankaran 2006-07-28 03:35:40 UTC
I want to use the two new attachments . 
I will provide the link to the attachments to be more clear

GPG - Key 
https://bugs.freedesktop.org/attachment.cgi?id=6336

SSH -key 

https://bugs.freedesktop.org/attachment.cgi?id=6337

Thank you 
Comment 9 Daniel Stone 2006-07-28 03:48:56 UTC
yes, I figured.  but attachment #6336 [details] still contains _two_ gpg keys.  which one
do you want to use?
Comment 10 Harishankaran 2006-07-28 04:20:05 UTC
Created attachment 6374 [details]
New gpg key

Sorry for the mistake . 
This time i have attached just one gpg key which i want to use .

Thank you for the reply
Comment 11 Daniel Stone 2006-08-01 01:17:23 UTC
created
Comment 12 Harishankaran 2006-09-05 06:15:07 UTC
I am not able to connect to either annarchy.freedektop.org neither
gabe.freedektop.org

the output i get when i do ssh -i .ssh/mykey sp2hari@annarchy.freedesktop.org -v

[alagu@npiu ~]$ ssh -i ~/.ssh/mykey sp2hari@annarchy.freedesktop.org -v
OpenSSH_4.0p1, OpenSSL 0.9.7f 22 Mar 2005
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to annarchy.freedesktop.org [131.252.208.36] port 22.
debug1: Connection established.
debug1: identity file /home/alagu/.ssh/mykey type 1
debug1: Remote protocol version 2.0, remote software version 3.9p1
debug1: no match: 3.9p1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'annarchy.freedesktop.org' is known and matches the RSA host key.
debug1: Found key in /home/alagu/.ssh/known_hosts:14
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/alagu/.ssh/mykey
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
Password:
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,keyboard-interactive).
[alagu@npiu ~]$

Here if i give my passphrase it is not working :( 
I think it should ask me for the passphrase here and not the password.

mykey.pub is what i uploaded while creating the freedesktop account 

I am able to change the passphrase of my keys by using 
ssh-keygen -p 
It asks for the old passphrase and i am able to change it . This means that i
have not screwed up my ssh keys right ?
Comment 13 Daniel Stone 2006-10-24 14:13:29 UTC
i must've been using the old public key; fixed.
Comment 14 Harishankaran 2007-06-18 23:48:30 UTC
Created attachment 10371 [details]
My PGP PUBLIC KEY

This is my pgp public key. Please add it to my account.
Comment 15 Harishankaran 2007-06-18 23:49:42 UTC
Have added the my pgp public key. Please add that to my account. 

Thanks . 
Comment 16 Vincent Untz 2007-06-21 09:13:13 UTC
Harishankaran: is this gpg key a new key to replace the old one? It's probably better to open a new bug.
Comment 17 Harishankaran 2007-06-21 11:15:18 UTC

*** This bug has been marked as a duplicate of bug 11327 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.