mkinitcpio-ykfde
Full disk encryption with Yubikey (Yubico key) (by eworm-de)
c-toxcore
The future of online communications. (by TokTok)
| mkinitcpio-ykfde | c-toxcore | |
|---|---|---|
| 2 | 20 | |
| 105 | 2,158 | |
| - | 0.5% | |
| 2.3 | 9.5 | |
| 4 months ago | 4 days ago | |
| C | C | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mkinitcpio-ykfde
Posts with mentions or reviews of mkinitcpio-ykfde.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-31.
-
sd-encrypt, LUKS partition unlock and YubiKey - Erratic behavior
I am interested in running a self-signed Secure Boot LUKS setup that I could unlock with my YubiKey. I've tried an initramfs hook in my other devices and it works. However, I read this section about unlocking the LUKS partition with systemd and its integrated enrollment tool (systemd-cryptenroll) and my interest was piqued since it meant an integrated solution that doesn't depend on a third-party one.
-
Second factor LUKS encryption via Yubikey on Fedora 33
Found a solution myself: https://github.com/eworm-de/mkinitcpio-ykfde/blob/master/README-dracut.md
c-toxcore
Posts with mentions or reviews of c-toxcore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-15.
- Tox Core is one of the nicest-to-read C codebases
-
uTox – The Lightweight Tox Client
See also this somewhat infamous thread on Tox's cryptographic design[1].
[1]: https://github.com/TokTok/c-toxcore/issues/426
-
Tox seems slowly dying (change my mind), what alternatives have you researched?
In case with Tox you have to trust in homebrew crypto that was never properly audited (how about that security issue reported by Donenfeld in 2017, which is being tackled only now, sort of?) -- and outdated and outright abandoned clients which were never above, let's say, "beta quality".
-
qTox unmaintained. Is this the end of qTox?
it has the new group chat feature (https://github.com/TokTok/c-toxcore/pull/2269)
-
Российские спецслужбы научились следить за пользователями Telegram
"If Tox already does onion routing, why use Tox over Tor?"
-
My list of favorite secure messaging apps
What an arbitrary criteria to judge a project by. There have been 5 releases in the past year, including a major feature release.
https://github.com/TokTok/c-toxcore/releases
-
I know Privacy Guides is the new version of Privacy Tools, but even if so, do the recommendations (or at least most of them) in the old site still apply today?
Signal isn't falling behind and Tox is an old service that has had issues with messages being spoofable since day 1
-
Shadiness in the Privacy Space: Jonah Aragon's (PrivacyGuides) Failed Attempt to Takeover PrivacyTools.io
tox https://github.com/TokTok/c-toxcore/issues/426
-
E2E encrypted voice and chat service similar to Discord/Slack?
You could use a Tox front end like qTox or Toxic. It is a fully encrypted end-to-end communication protocol that allows text, voice, and video chat. The github page for the Tox protocol has some useful caveats about the its security.
-
Tox: Decentralized and Encrypted Instant Messaging
It links to a bug report discussion where one of the developers states that they don't understand the security properties of tox very well[1].
I find that worrying.
[1] https://github.com/TokTok/c-toxcore/issues/426