As someone who know pgp exists, i say have at it feds, lets see what kind of explots clippy2.0 has and how quickly it gets cracked.

Seriously ever actual expert in cryptography would tell then what they want is not possible. It would be exploited within weeks, probably by multiple different actors. Let them fuck around and find out, they obviously dont “learn” from it, but at least it will shut them down for another decade or so.

You can set it to wipe them from memory on different conditions, including instantly if youre that paranoid, sure its still possible. Its an optional feature most people wont use, but its pretty well thought out.

Molly encrypts it using a passphrase instead of a locally stored key for exactly that reason.

The EFF maybe, but the USAs lack of a GDPR equivalent makes it harder.

The problem is that while docker is running as root (0) the searxng process internally runs as a user searxng with id 977

So your filesystem outside of docker needs to have those files assigned the right ownership.

This thread has a more detailed discussion that you might find helpful. https://forums.truenas.com/t/how-to-install-searxng-app-docker-permissions-issue/14049/10

Yep Probably you need to change ownership and/or permissions of the files outside of docker.

I dont want to give the wrong suggestion from memory so hopefully thats enough info to get you going in the direction of a fix. Basically see what user id owns the files inside of docker, make it the same uid outside of docker in the folder you are bind mounting.

If you have permissions then try editibg uwsgi.ini and see if it lets you save.

Im going from memory but i think i had a similar issue and i had to manually create the file, yours shows the file already exists but it might not be writable.

try opening a shell with ’ docker exec -it searxng sh" and see if you can cat the file from inside docker, if yes then I’m not sure of a solution ,if no then the problem is with permissions on your filesystem outside of docker where you have " - ./data/searxng:/etc/searxng" You need to go to ./data/searxng and correct the permissions so they can be read inside the docker.

open(“/etc/searxng/uwsgi.ini”): Permission denied [core/io.c line 525]

I think here is your problem. Make sure that file exists and is readable from inside of the docker.

deleted by creator

“Digital Violence”

Are they playing video games?

Very poor choice of wording if you want people to take it seriously.