www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Clelland (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7574) Cannot reset password -- id.apache.org not responding
Date Mon, 14 Apr 2014 19:32:18 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968722#comment-13968722
] 

Ian Clelland commented on INFRA-7574:
-------------------------------------

Investigating this, it looks like I can access the server from other networks. From our internal
network, I can ping the server, but I cannot access it on ports 80 or 443. I suspect that
some kind of anti-abuse filter has kicked in and banned the Google Waterloo office.

(Possibly because agrieve tried to use a reset token that was more than 15 minutes old, the
hacker.)

Can someone check to see if our IP (74.125.59.33) has been added to any sort of blacklist
on id.apache.org?

> Cannot reset password -- id.apache.org not responding
> -----------------------------------------------------
>
>                 Key: INFRA-7574
>                 URL: https://issues.apache.org/jira/browse/INFRA-7574
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: LDAP
>            Reporter: Ian Clelland
>            Priority: Blocker
>
> I am attempting to reset my password in response to the heartbleed mass-reset. [https://wiki.apache.org/general/HeartBleed]
> The email I get directs me to a URL at id.apache.org, with a URL valid for 15 minutes,
but I cannot open the link. The http/s service on id.apache.org appear to be timing out.
> Not sure if this is a DoS issue caused by 6000 apache committers trying to reset their
passwords at the same time, or if the service is actually down. Regardless, I cannot commit
anything to the git repos because I cannot reset my password.
> (Considering that I used a page at id.apache.org to /request/ that reset link, it appears
that this is a new situation)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message