You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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).
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 …
The text was updated successfully, but these errors were encountered: