hey guys i've a question, when using age to define a secret inside a home manager module, is there anything extra I need to do to have the secret available under the home agenix path? i have something like this in my home manager config:

programs.atuin = {
  enable = true;
  key_path = config.age.secrets.atuinKey.path;
}

age.secrets.atuinKey.file = inputs.self + /secrets/atuinKey.age;

In reply to@willpower3309:matrix.org
Hey all! Interesting question here - how many private keys would need to be known to be able to determine what the other keys that a secret is encrypted with are? Lets say I had a secret encrypted to 3 different hosts' private keys, with the public keys of those hosts known. If someone figured out one of my host's private keys, could they then determine my other hosts' private keys given the knowledge of the secret and the public keys of those hosts?

Hi, I hope somebody here might be able to help me even though it might be slightly off-topic:
I just configured agenix-rekey for my secret management together with my yubikey. Everythings works, but I don't know whether my identity file is correct like this:

#       Serial: XXXXXXXX, Slot: 1
#         Name: age identity XXXXXXXX
#      Created: Fri, 08 Nov 2024 18:38:59 +0000
#   PIN policy: Never  (A PIN is NOT required to decrypt)
# Touch policy: Cached (A physical touch is required for decryption, and is cached for 15 seconds)
#    Recipient: age1yubikeyXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AGE-PLUGIN-YUBIKEY-XXXXXXXXXXXXXXXXXXXXXX

As far as I understood this only contains public key information and is save to be committed (in theory publicly). If not how do I split the public and private part?