News for hackers. Stuff that matters.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by ccakes on Thursday October 13, 2022 @05:23PM (#33196675)
You can invite by email addr, so the workaround here is only invite corporate email addresses.

If the target user hasn't added their corp email to their profile then they can't be part of the org.

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by prepend on Thursday October 13, 2022 @06:07PM (#33197081)
This is what I do but I really wish there was a better integration with auth providers and could use it for the invite. Would be nice to search my directory to type the email and confirm the name matches the email.

This is what GitLab does with their hosted AD/LDAP connector.

I’m in fear of mistyping something and inviting the wrong person.

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by dotancohen on Thursday October 13, 2022 @06:27PM (#33197293)
So never type an email address in at all. Go to an extent email message, copy the bloke's email address, then paste it into the Github interface.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by EE84M3i on Thursday October 13, 2022 @08:05PM (#33198115)
This can be vulnerable to "ticket trick" - often support/helpdesk sites are put on the main domain and have reply-to email addresses that will reflect the content back to the user requesting support. This can be used to sign up for slack, etc.