]>
Commit | Line | Data |
---|---|---|
1 | --- | |
2 | author: christel | |
3 | date: 2016-12-20 05:30:34+00:00 | |
4 | slug: PSA-brief-update-infra | |
5 | title: A brief security update from the infrastructure team | |
6 | category: community | |
7 | category: security | |
8 | category: freenode | |
9 | category: technical | |
10 | --- | |
11 | ||
12 | A freenode volunteer has identified and responded to a suspected compromise of their e-mail accounts, which could have provided | |
13 | an unauthorised user with limited access to some data sent via internal e-mail systems (this could include support tickets or | |
14 | internal communications). | |
15 | ||
16 | Naturally, we instigated audit procedures immediately so as to ensure the security of the production network and accompanying | |
17 | infrastructure. The investigation is ongoing, but at this time we have no reason to believe that any other unauthorised access | |
18 | was gained. Nevertheless, in the interests of transparency and security for our users, we wish to notify anyone who may have | |
19 | been affected. | |
20 | ||
21 | As always, we would still recommend that you ensure that you change any passwords to freenode systems, and be alert to any | |
22 | suspicious activity on your account. We would additionally always recommend that you not share passwords between accounts, | |
23 | especially those spanning multiple providers (please ensure you have a registered e-mail address before changing your password | |
24 | so that it can be reset!). | |
25 | ||
26 | We will provide further updates if it becomes appropriate to do so; please rest assured that we take the security and privacy | |
27 | of our users very seriously, and work with industry experts and law enforcement where appropriate to investigate and respond | |
28 | to possible security breaches. |