Stars and mentions
Last 30 days, Oct 4 – Nov 2
Package downloads
Top repositories
jtesta’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside jtesta’s account where jtesta opened or reviewed pull requests in the past 365 days.
Who noticed jtesta
Everyone who starred or forked jtesta’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 0Owned by jtesta now
No trending awards yet
None of the repositories jtesta owns has finished in the top three of a completed trending day or week, by stars, forks or PR authors. See who is trending now.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Great news. I've seen interop issues with people disabling ECDSA for these worries, and I often run into incompatibilities between protocols that only support ed25519, and my hardware tokens/TPMs that only support ECDSA. I have tried in vain to get projects to allow ECDSA (consistent with prevailing consensus), to address these interop issues. Hopefully this will persuade jtesta/ssh-audit to not flag ECDSA, also a source of interop issues. > This contributed to enduring conspiracy theories, which had significant appeal among the non-specialist public (although many have since moved on to other, adjacent, conspiracy theories). All this speculation harmed confidence in robust cryptographic systems and was part of my motivation for the bounty. > > This week’s findings completely rule out the technique described by Bernstein and Lange. This feels a bit harsh? If it was only this week's findings that completely ruled this out, was it so irrational to have been sceptical about ECDSA? After all, as the author persuasively argues in their post on accelerated PQC timelines: > If you are thinking “well, this could be bad, or it could be nothing!” I need you to recognize how immediately dispositive that is. The bet is not “are you 100% sure a CRQC will exist in 2030?”, the bet is “are you 100% sure a CRQC will NOT exist in 2030?” [...] Remember that you are betting with your users’ lives.
Trying to connect to a Dropbear SSH server may give the "** WARNING: connection is not using a post-quantum key exchange algorithm." warning. This might be a false positive, as this Github issue suggests: ssh-audit#375 [1/2]