nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1ycnhgr56efxcpvhu7q0er9gqjqttpwhgqgjfgjaj7gpfea5g6xhq4zgshs ok, but understand that means all the secrets are effectively on disk at /proc/self/environ. An arbitrary file read (like the two recent Pleroma issues) means full secret disclosure.

I would really recommend against it.

Ditto will only support uploading through s3 and it won't support XML. It will even crash if you try to configure the media domain the same as the root domain.

Reply to this note

Please Login to reply.

Discussion

Security through instability?

nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1ycnhgr56efxcpvhu7q0er9gqjqttpwhgqgjfgjaj7gpfea5g6xhq4zgshs did you reply to the wrong thread? I don’t know what this has to do with not storing secrets in envvars

Instead of crashing, just don't allow users to do it 🤣

Maybe provide full gui configuration screen with the ability to use an api similar to Mastodon api. Just make sure the api isn't retarded like Mastodon api.