Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Request for Enforcing Two-Factor Authentication for All Committers

Hi Ivar,

Thank you for your response. If we enforce 2FA at the organization level (i.e. for https://github.com/jakartaee/ and https://github.com/eclipse-ee4j/), it means that committers without 2FA activated would be kicked out of the organization until they actually enable it. See docs from GitHub (https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)

  • When you require use of two-factor authentication for your organization, members, outside collaborators, and billing managers (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their personal account within three months of their removal from your organization.
  • If an organization owner, member, billing manager, or outside collaborator disables 2FA for their personal account after you've enabled required two-factor authentication, they will automatically be removed from the organization.

Let me know what's the PMC decision.

Thanks again!

Mikaël Barbero 
Head of Security | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration



On 2 Mar 2023, at 23:52, Ivar Grimstad via ee4j-pmc <ee4j-pmc@xxxxxxxxxxx> wrote:

Unless there are objections among the PMC members, I'd say go ahead and activate it for all EE4J repositories. 

Ivar 

On Thu, Mar 2, 2023, 12:13 Mikael Barbero via ee4j-pmc <ee4j-pmc@xxxxxxxxxxx> wrote:
Dear EE4J/JakartaEE PMC Team,

I am reaching out to request that your project enforces two-factor authentication (2FA) for all committers at GitHub. We, at the Eclipse Foundation, take the security of your project's code and data very seriously. Enforcing 2FA can greatly improve the security of your project and protect it from potential security breaches.

As you may know, 2FA adds an extra layer of security to the login process by requiring users to provide two forms of authentication: something they know (such as a password) and something they have (such as a security key or smartphone). This significantly reduces the risk of unauthorized access to sensitive information, as it makes it much more difficult for hackers to gain access to user accounts. With the increasing number of security breaches and cyberattacks, it is crucial for open source projects to take extra precautions to secure their code and data. Enforcing 2FA for all committers would be a simple yet effective way to enhance the security of your project. See a blog post of mine for additional details: https://mikael.barbero.tech/blog/post/2022-11-22-2fa-for-developers/

We understand that implementing 2FA may require some effort, but we are here to help. If you want to start enforcing it, just open a ticket on the Eclipse Foundation help desk. I can already tell you just above 60% of committers have 2FA activated on both jakartaee and ee4j GitHub organizations.

Finally, I would like to remind you that GitHub will eventually enforce 2FA for all projects by the end of the year. Take the lead on that and start right now!

Thank you for your time and consideration. I look forward to your response.

Cheers,


Mikaël Barbero 
Head of Security | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration



_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc

Attachment: signature.asc
Description: Message signed with OpenPGP


Back to the top