Försvarsmakten rustar. Antalet värnpliktiga ska kraftigt öka under de kommande tio åren. Men alla som kallas till mönstringen vill inte göra värnplikten.

Which is the best alternative to typage? Based on common mentions it is: Age, Sops, Git-crypt, Rage, C2SP, Agenix, Kryptor, Awesome-age, Arcxio/Urn or Agenix-rekey

Kryptoraset tilltar - detta händer nu| Håll dig uppdaterad med aktuella ekonominyheter – gratis.

I couldn’t agree more — Valsorda’s and Latacora’s articles are very convincing and are widely quoted by professionals. It’s kind of ironic that Privacy Guides still recommends Kryptor, abandoned by its author, but doesn’t recommend age.

Kryptor FPGA, sometimes just called Kryptor, is a compact Intel/Altera MAX10 FPGA development board mostly designed for encryption, and acting as a

I seem to remember age didn’t do the sender authenticity which is what Kryptor was specifically designed to address, so if you’re signing the file you’d still need to use minisign as well. In terms of focus/exposure it does **a lot less** than PGP does so, you can expect it to possibly reach a “feature complete” status. Given Samuel’s experience, and the fact that he is still active it may just be very well he hasn’t had to add anything to it. There are not any open issues on this tool or pull requests. jonah: > I am surprised we don’t recommend age (or minisign) though, I thought we did. This seems to be @dngray’s thing though, so maybe he can elaborate: The reason is because we’d need to provide a guide to go along with it, as it’s not an all in one process whereas Kryptor is. However on further look, Kryptor does depend on a vulnerable version of libsodium which will flag CVE analysis tools for CVE-2025-69277. While this may not effect the tool itself, perhaps a guide utilizing age and ssh key signatures is a simpler way to go about it.

I think for your use-case age, GnuPG (symmetric encryption mode), Kryptor, Picrocrypt or Picrocrypt-NG would be a better way of doing it as it seems that your goal is just do encrypt your files before uploading them. These tools do exactly that, and VeraCrypt is not made for that. Especially if you need „absolute certainty"

The author of Kryptor was very active on PG discussions when they were still on Github. While it is surely a cool tool but PG at the time has not really considered fhe importance of a third party audit on software. I do think for the purpose of what we are dealing with here that should be something to consider making a requirement.

Kryptor has now not had a commit in over two years it seems. I think it might be time to look at removing it. @team

The issues with OpenPGP (cryptographic message packets) and GnuPG (command line tool) can be read about in other threads and elsewhere. While OpenPGP and GnuPG are still used widely, for instance in email and to sign git commits, I see some merit in adopting cryptographic tools that are simpler and more secure and eventually deprecating OpenPGP/GnuPG for file encryption and signing. I see Kryptor is recommended for file encryption and signing, but not other tools like age and minisign. I see some merit in recommending a tool that does both encryption and signing, and limiting the number of listed recommendations. By using Kryptor, users don’t need to manage separate keys that are used by separate tools. Age does encryption only and minisign does signing only, thus in a way it makes sense to recommend Kryptor over age and minisign. Kryptor’s homepage makes claims about other merits over age and minisign, some of which I agree with. That said, I wish to understand what other considerations were made when Kryptor was added as a recommendation, and if justified, have the recommendation reconsidered. I briefly looked at Kryptor, age and minisign, and found this. Kryptor appears to have been developed mainly by just 1 dev. 2 contributors are listed on GitHub but I didn’t easily find any commits by the other contributor (but I did find 2 pull requests by others). This suggests Kryptor is essentially developed by 1 dev, samuel-lucas6, a cybersecurity Master student. In comparison, age has 54 listed contributors, and the main dev FiloSottile is a cryptographer who maintains Go’s cryptography. Minisign has 24 listed contributors, and the main dev jedisct1 developed and maintains libsodium. As of now, Kryptor’s latest public commit on GitHub was made January 12, 2025, 7 months ago. The latest closed issue was closed July 16, 2024, over 1 year ago. In comparison, age has recent commits, and their latest closed issue was 3 months ago and their merged pull request was 2 months ago. Minisign has recent commits, and their latest closed issue and merged pull request were 1 month ago. * Kryptor GitHub * age GitHub * minisign GitHub I didn’t find security audits for Kryptor, age or minisign. I haven’t considered the design and features of each tool in depth, inspected the code myself for quality, nor considered the character of each project’s community.

Yeah I would absolutely prefer Denis’ Minisign, but the thing is it’s not bundled by AFAIK any Linux distro, which is a decent requirement for verifying software signatures. E.g. https://www.kryptor.co.uk/ has detached signatures that use… kryptor : ) Talk about a bootstrapping problem. Yeah the SHA256 are probably fine, especially if you have the site’s TLS certificate fingerprint pinned somewhere. Oh what’s that? It changes every three months? age and minisign at least install via apt, which is a bit better. So yeah teaching any those is not a bad idea because when the best one gains popularity, it incentivizes distro vendors to bundle it.

maqp: > PGP still has one good use purpose. You should learn to digitally sign files with it: Dhole Moments – 15 Nov 24 ### What To Use Instead of PGP - Dhole Moments It’s been more than five years since The PGP Problem was published, and I still hear from people who believe that using PGP (whether GnuPG or another OpenPGP implementation) is a thing they s… PGP isn’t the best option for that either, there’s Sigstore, Minisign, and Kryptor