Re: [Tools-team] Agenda for the 14 June 2006 Teleconference

Hi Tero,

on 2006-06-14 18:58 Tero Kivinen said the following:
> Henrik Levkowetz writes:
>> 2. Status review
>> 
>>    * Dashboard
>> 	- Henrik
> 
> Some comments about loginmgr.
> 
> 1) That login manager really needs to require TLS protection, i.e
>    mandate that both the forms and the posts are always using TLS.

Yes.  But to do that, I need a proper cert for tools.ietf.org, which
I don't have.  I've been planning to talk with Ray about it for some
time, but no time...  I assume that this has to go through some
entity that can verify that we have a right to get a cert for
tools.ietf.org.   I also wonder if we need separate certs for
tools.ietf.org, www1.tools.ietf.org, www2.tools.ietf.org and www3.tools.ietf.org...

> 2) The URL for changing password should only work exactly once, not
>    for 24 hours. The problem with 24 hours is that if someone manages
>    to get the URL later from my mailbox or some other place he can
>    change my password after I changed it. If it works exactly once,
>    either I will get error that password has already been changed
>    using the URL (i.e. I know there was attacker who stole my URL) or
>    the attacker cannot change my password after I have successfully
>    changed it. Perhaps storing the used auth sha1sum to some directory
>    and checking that it cannot be there before continuing.

I agree, and this is already on my todo list, but I wanted to get the
base functionality out there first.  This can be accomplished without
changing what I have now, only putting in an additional check in the
script which verifies the hash.

Something else which you haven't mentioned but is also on my todo list
is rate limiting on requesting the mail with a new password URL, so
people can't anonymously annoy others with a stream of mails with
new password URLs.

Thanks for the feedback :-)

	Henrik

Re: [Tools-team] Agenda for the 14 June 2006 Teleconference

Attachment: signature.asc