Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private keys from Fortigate leak #117

Open
BenBE opened this issue Jan 17, 2025 · 2 comments
Open

Private keys from Fortigate leak #117

BenBE opened this issue Jan 17, 2025 · 2 comments

Comments

@BenBE
Copy link
Collaborator

BenBE commented Jan 17, 2025

Based on https://blog.hboeck.de/archives/908-Private-Keys-in-the-Fortigate-Leak.html

@hannob : Please add the affected (private) keys here once you decide to publish them.

No need to hurry, this issue is mostly for tracking …

@BenBE BenBE changed the title Private keys from Fortinet leak Private keys from Fortigate leak Jan 17, 2025
@hannob
Copy link
Collaborator

hannob commented Jan 19, 2025

The number of keys is large enough that they should go in a separate repo. As discussed before, I think it's good that the main "kompromat" repo is of a manageable size, so cloning it doesn't take exceptionally long.

I'll probably just publish them on my own, but you're of course free to fork / re-host that repo once I do.

@BenBE
Copy link
Collaborator Author

BenBE commented Jan 19, 2025

We also could add a second repo to this organization hosting these keys. That way they are kinda together. Similar could also be done for the split-out Debian OpenSSL keys (although technically they are still in this repo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants