age VS Kryptor

age

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.

Bit new to this, but would it be possible to have Peazip as a frontend that supports Xchacha20? I believe it could interface with something like Kryptor here: https://www.kryptor.co.uk/

i am currently packaging https://github.com/samuel-lucas6/Kryptor. i already tried building it from source, but i got an error and nobody was able to help me. so i am now resorting to just packaging the supplied blob.

And I have yet to write my own file encryption tool… At least others are doing it for me.

{ lib, fetchFromGitHub, fetchzip, stdenvNoCC, dotnetCorePackages, buildDotnetPackage}: let repo = fetchzip { url = "https://github.com/samuel-lucas6/Kryptor/archive/refs/tags/v4.0.1.zip"; sha256 = "sha256-SK4TZg/T6SFimF83iwv3dqTkxDuhk7D7GSWg+oybrDg="; }; in buildDotnetPackage rec { pname = "kryptor"; version = "4.0.1"; src = "${repo}/src"; }

I think depends what be needed, but the main thing is full system encryption. I don't need encrypt single & multiple files, if they are stored on encrypted drive. If I must move them, I can use USB drive encrypted by VeraCrypt. If be needed, I can encrypt all files using Age or Kryptor. Usually Kryptor is recommended more often than Age as I saw, because it's "easier" but I think if something is older could be better, because was more time to detecting errors. 12k vs 1k starts on GitHub is really huge differences in favor of the Age.

I want to ask about algorithms used in that tools: Picocrypt, Kryptor and Hat. I think which one tools should I chose and when. With my knowledge, theoretically the best option are Picocrypt and Hat, depends on situation.

I tested a few encryption open-source software programs: Picocrypt, hat.sh and Kryptor. I combine it all together, and my TXT file looks now that: hello.pcv.enc.pcv.kryptor.

This article is a pretty garbage.

> There is no need to use Git source code management if you don't need it. Git's a complicated tool, which is why Linus Torvalds gave it the name: it's British English for a hostile or uncooperative person. 7-Zip has a single author, Igor Pavlov, and if he doesn't want to use Git, The Reg FOSS desk doesn't blame him.

Who cares if a media desk doesn't know how to use Git. How is that even relevant to the story.

Nobody has said that he should use git, but it is a good idea to use some kind of version control so that changes to the code can be easily tracked, based on change. Places like Github, Gitlab provide plenty of documents.

Using version control also encourages others to contribute. 7-Zip in itself is very old C++ code that I doubt anyone has really looked at too closely in a long time.

Further it often gets recommended as an "encryption tool" when there are better modern alternatives such as Picocrypt https://github.com/HACKERALERT/Picocrypt or Kryptor https://www.kryptor.co.uk.

They later mention that bullshit node-ipc pulled, yet they don't see how version control provides accountability.

Amusing.

You might want to look at Kryptor for something minimal that is actually usable in a reasonable way.