On 8 October 2015 at 04:58, Benjamin Peterson wrote:
> On Wed, Oct 7, 2015, at 19:38, Tim Peters wrote:
>> [Benjamin Peterson ]
>> > As a followup to this, I have now removed all DSA keys. People who only
>> > had DSA keys will need to submit new keys to hgaccounts@.
>>
>> That apparently was addr
On 10/8/2015 1:20 PM, Brett Cannon wrote:
> You will
> always get a reply email from whomever installs your new key that it was
> done and that you should test it.
Perhaps follow
"29. How do I generate an SSH-2 public key?
All generated SSH keys should be sent to hgaccou...@python.org for
addi
On 10/8/2015 1:20 PM, Brett Cannon wrote:
I personally know Terry's key has not been installed yet. You will
always get a reply email from whomever installs your new key that it was
done and that you should test it.
Ignore the one I sent 12 hours ago: it was still DSA though with more
bits. I
People are reading it, just a matter of people having a checkout and time
to get to the keys. If no one beats me to it I will personally work through
the backlog tonight.
On Thu, 8 Oct 2015 at 10:07 Terry Reedy wrote:
> On 10/7/2015 10:38 PM, Tim Peters wrote:
> > [Benjamin Peterson ]
> >> As a
I personally know Terry's key has not been installed yet. You will always
get a reply email from whomever installs your new key that it was done and
that you should test it.
This manual key management is yet another reason why we are going to get a
new development process *somehow* in 2016.
On Th
[Terry Reedy , on SSH keys]
> I sent a new one about 11 hours ago. I am still getting
> Putty Fatal Error
> Disconnected: No supported authentication methods available
> (server sent: publickey)
>
> Is anyone tending the mail box, or do I have to do something else?
My new one got installed about
On 10/7/2015 10:38 PM, Tim Peters wrote:
[Benjamin Peterson ]
As a followup to this, I have now removed all DSA keys. People who only
had DSA keys will need to submit new keys to hgaccounts@.
I sent a new one about 11 hours ago. I am still getting
Putty Fatal Error
Disconnected: No supported
On 8 October 2015 at 03:58, Benjamin Peterson wrote:
>> Just noting that the Windows section of the devguide:
>>
>> https://docs.python.org/devguide/faq.html
>>
>> should probably be changed to say something other than the current:
>>
>> Use PuTTYgen to generate your public key. Choose the
On Wed, Oct 7, 2015, at 19:38, Tim Peters wrote:
> [Benjamin Peterson ]
> > As a followup to this, I have now removed all DSA keys. People who only
> > had DSA keys will need to submit new keys to hgaccounts@.
>
> That apparently was addressed to me - cool ;-)
>
> Just noting that the Windows s
On Wed, Oct 7, 2015, at 18:52, Raymond Hettinger wrote:
>
> > On Oct 6, 2015, at 11:43 PM, Benjamin Peterson wrote:
> >
> > As a followup to this, I have now removed all DSA keys. People who only
> > had DSA keys will need to submit new keys to hgaccounts@.
>
> That was rather sudden and hars
[Benjamin Peterson ]
> As a followup to this, I have now removed all DSA keys. People who only
> had DSA keys will need to submit new keys to hgaccounts@.
That apparently was addressed to me - cool ;-)
Just noting that the Windows section of the devguide:
https://docs.python.org/devguide/faq
> On Oct 6, 2015, at 11:43 PM, Benjamin Peterson wrote:
>
> As a followup to this, I have now removed all DSA keys. People who only
> had DSA keys will need to submit new keys to hgaccounts@.
That was rather sudden and harsh.
Effectively, you just revoked my commit rights.
I'll wrestle with th
Do realize, though, that simply asking hgaccounts to take the keys from
your GitHub key URL might not get you what you expect if you use GitHub
Desktop as that app installs its own keys.
On Wed, 7 Oct 2015 at 03:05 Nick Coghlan wrote:
> On 7 October 2015 at 13:43, Benjamin Peterson wrote:
> >
On 7 October 2015 at 13:43, Benjamin Peterson wrote:
> As a followup to this, I have now removed all DSA keys. People who only
> had DSA keys will need to submit new keys to hgaccounts@.
And for folks looking for an authenticated way of passing along key
details, if you have a GitHub account, Git
As a followup to this, I have now removed all DSA keys. People who only
had DSA keys will need to submit new keys to hgaccounts@.
On Thu, Aug 27, 2015, at 13:36, Georg Brandl wrote:
> Hi all,
>
> newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for
> public key authentication.
On Tue, Sep 1, 2015 at 2:02 AM, Antoine Pitrou wrote:
> By the way, for those who have been scratching their heads under Linux
> with unhelpful behaviour from the desktop's keyring, it turns out
> gnome-keyring hasn't been updated for ed25519 support...
>
> https://bugzilla.gnome.org/show_bug.cgi
> Even better: send a ed25519 key as documented in the devguide.
By the way, for those who have been scratching their heads under Linux
with unhelpful behaviour from the desktop's keyring, it turns out
gnome-keyring hasn't been updated for ed25519 support...
https://bugzilla.gnome.org/show_bug.c
On Thu, Aug 27, 2015, at 16:36, Donald Stufft wrote:
> On August 27, 2015 at 4:37:21 PM, Georg Brandl (g.bra...@gmx.net) wrote:
> > Hi all,
> >
> > newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for
> > public key authentication. If you experience "permission denied" errors,
On August 27, 2015 at 4:37:21 PM, Georg Brandl (g.bra...@gmx.net) wrote:
> Hi all,
>
> newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for
> public key authentication. If you experience "permission denied" errors,
> this (currently) comes from the client side only and hg.python
Hi all,
newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for
public key authentication. If you experience "permission denied" errors,
this (currently) comes from the client side only and hg.python.org will
accept these keys if you enable them using the PubkeyAcceptedKeyTypes
opt
20 matches
Mail list logo
