flathub / flathub/org.gnu.emacs
SSH / SSL Libraries in Sandbox
- Dominant language
- No language data
- Stars
- 18
- Forks
- 20
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 1
Description
The emacs flatpak has some issues specific to eshell trying to access shared binaries such as ssh-add.
If you attempt to add an ssh key via:
$> ssh-add
You'll get an error in the form of:
`/var/run/host/usr/bin/ssh-add: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory`
Which makes sense, eshell can see the binary but said binary cannot see its shared library in the hosts /usr/lib.
There's probably a few ways to handle this but it probably makes sense to simply pass these libraries to the sandbox? I think this just requires:
` "--socket=ssh-auth",`
But I'm unfamiliar with flatpak in general.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.