Real Name : Siraj Razick Account Name : siraj email : siraj.razick@collabora.co.uk
Created attachment 55398 [details] rsa public key
Created attachment 55399 [details] pgp public key
You appear to have attached two equally-strong (RSA+RSA, 2048-bit) PGP public keys, 2C2B4CAA (created yesterday) and 7E5AD8AD (created in May). Neither has any third-party signatures on it, and neither is present on the synched keyserver network: reptile% gpg --list-sigs 2C2B4CAA pub 2048R/2C2B4CAA 2012-01-10 uid Siraj Razick (Software Eng at Collabora) <siraj.razick@collabora.co.uk> sig 3 2C2B4CAA 2012-01-10 Siraj Razick (Software Eng at Collabora) <siraj.razick@collabora.co.uk> sub 2048R/A0897409 2012-01-10 sig 2C2B4CAA 2012-01-10 Siraj Razick (Software Eng at Collabora) <siraj.razick@collabora.co.uk> reptile% gpg --list-sigs 7E5AD8AD pub 2048R/7E5AD8AD 2011-05-17 uid Siraj Razick <siraj.razick@collabora.co.uk> sig 3 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> uid Siraj Razick (Software Developer at Collabora Ltd) <siraj.razick@collabora.co.uk> sig 3 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> sub 2048R/85FF2A3C 2011-05-17 sig 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> reptile% gpg --recv-keys 2C2B4CAA 7E5AD8AD gpg: requesting key 2C2B4CAA from hkp server the.earth.li gpg: requesting key 7E5AD8AD from hkp server the.earth.li gpgkeys: key 2C2B4CAA not found on keyserver gpgkeys: key 7E5AD8AD not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 Which key do you intend to be using for freedesktop.org? ---- Additional things that do not block creation of an fd.o account: please consider uploading your chosen key to the public keyserver network (wwwkeys.pgp.net), and get some signatures on it if possible (e.g. next time you go to a conference).
Created attachment 55465 [details] the correct pgp public key correct pgp-public key
(In reply to comment #3) > You appear to have attached two equally-strong (RSA+RSA, 2048-bit) PGP public > keys, 2C2B4CAA (created yesterday) and 7E5AD8AD (created in May). Neither has > any third-party signatures on it, and neither is present on the synched > keyserver network: > > reptile% gpg --list-sigs 2C2B4CAA > pub 2048R/2C2B4CAA 2012-01-10 > uid Siraj Razick (Software Eng at Collabora) > <siraj.razick@collabora.co.uk> > sig 3 2C2B4CAA 2012-01-10 Siraj Razick (Software Eng at Collabora) > <siraj.razick@collabora.co.uk> > sub 2048R/A0897409 2012-01-10 > sig 2C2B4CAA 2012-01-10 Siraj Razick (Software Eng at Collabora) > <siraj.razick@collabora.co.uk> > > reptile% gpg --list-sigs 7E5AD8AD > pub 2048R/7E5AD8AD 2011-05-17 > uid Siraj Razick <siraj.razick@collabora.co.uk> > sig 3 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> > uid Siraj Razick (Software Developer at Collabora Ltd) > <siraj.razick@collabora.co.uk> > sig 3 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> > sub 2048R/85FF2A3C 2011-05-17 > sig 7E5AD8AD 2011-05-17 Siraj Razick <siraj.razick@collabora.co.uk> > > reptile% gpg --recv-keys 2C2B4CAA 7E5AD8AD > gpg: requesting key 2C2B4CAA from hkp server the.earth.li > gpg: requesting key 7E5AD8AD from hkp server the.earth.li > gpgkeys: key 2C2B4CAA not found on keyserver > gpgkeys: key 7E5AD8AD not found on keyserver > gpg: no valid OpenPGP data found. > gpg: Total number processed: 0 > > Which key do you intend to be using for freedesktop.org? > > ---- > > Additional things that do not block creation of an fd.o account: please > consider uploading your chosen key to the public keyserver network > (wwwkeys.pgp.net), and get some signatures on it if possible (e.g. next time > you go to a conference). HI :) thanks for the review , I reattached the pgp key with one pub key.. which I'll be using (2C2B4CAA). I asked some friends/colleges to sign this already. BR Siraj
Please give Siraj an account and add it to the 'telepathy' group.
Account created, welcome and sorry for the delay.
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.