From: Carlos O'Donell <codonell@redhat.com>
To: Stafford Horne <shorne@gmail.com>, overseers@sourceware.org
Subject: Re: Password Reset
Date: Mon, 02 Dec 2019 18:20:00 -0000 [thread overview]
Message-ID: <a41ca831-09ea-f66e-56d6-8c1fec459cf3@redhat.com> (raw)
In-Reply-To: <CAAfxs76Judqv34RZ-23fDGAYeMPGtkEJam6B99OCNVeLpFGPrA@mail.gmail.com>
On 12/2/19 2:34 AM, Stafford Horne wrote:
> Hello,
>
> On Mon, Dec 2, 2019, 2:09 PM Christopher Faylor <
> cgf-use-the-mailinglist-please@sourceware.org> wrote:
>
>> On Mon, Dec 02, 2019 at 07:22:05AM +0900, Stafford Horne wrote:
>>> I seem to have forgot the password for my sourceware account:
>> shorne@sourceware.org,
>>> or it is locked.
>>>
>>> I have tried to use the reset password function on bugzilla but it
>> doesn't seem
>>> to work. There is a bugzilla bug I need to attend so I am trying to get
>> my
>>> access working.
>>>
>>> Please help.
>>
>> sourceware access doesn't use passwords. It uses ssh keys.
>>
>> Your public ssh key on file starts with:
>>
>>
>> AAAAB3NzaC1yc2EAAAADAQABAAABAQC7JvvqRSDTQZcLYiQXMQ/o4F8yYGxeCrAV+Cdua7/xunM9f
>>
>
> My ssh Access is fine. I am asking about the bugzilla password.
Have you tried using the "Forgot Password" link in bugzilla?
Go here: https://sourceware.org/bugzilla/
Top right click "Forgot Password"
Enter your email.
Click "Reset Password"
Wait for your email to arrive.
Then follow the password reset instructions.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-12-02 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 22:22 Stafford Horne
2019-12-02 5:09 ` Christopher Faylor
2019-12-02 7:34 ` Stafford Horne
2019-12-02 18:20 ` Carlos O'Donell [this message]
2019-12-02 18:49 ` Frank Ch. Eigler
2019-12-02 21:34 ` Stafford Horne
-- strict thread matches above, loose matches on Subject: below --
2014-07-22 13:27 password reset Cellier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a41ca831-09ea-f66e-56d6-8c1fec459cf3@redhat.com \
--to=codonell@redhat.com \
--cc=overseers@sourceware.org \
--cc=shorne@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).