You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.
Poking around a bit showed it was getting the <openssl/bio.h> header from my machine's installed libraries instead of the locally built copy. Uninstalling libssl-dev on my machine let it work properly, but since other packages (e.g. node) depend on it (and just generally the build script shouldn't be looking there), this isn't a general solution.
I'm currently fixing shadow/shadow#423, but depending on how long that takes I might be able to see what's going on and fix this.
The text was updated successfully, but these errors were encountered:
Although, the new version might cause other issues to appear, so I'm not sure if that is the best approach (although we should probably upgrade at some point.)
I wonder if we still need to build libevent or openssl thanks to elf loader namespaces, as long as we already have the OS provided packages. I haven't tried yet if that actually works.
For libevent, we want to intercept the dns function.
For openssl, we still want to intercept the crypt and cipher functions to avoid unnecessary computation.
The test would be to link to the OS provided packages and break on those preloaded functions to see if they still get called.
Fixed include and lib paths when configuring libevent. Now references
the customized openssl library in $(HOME)/.shadow instead of the
default one. This PR should fix issue #55.
After updating my lab machine to Ubuntu 18.04, libevent stopped building successfully:
Poking around a bit showed it was getting the
<openssl/bio.h>
header from my machine's installed libraries instead of the locally built copy. Uninstallinglibssl-dev
on my machine let it work properly, but since other packages (e.g. node) depend on it (and just generally the build script shouldn't be looking there), this isn't a general solution.I'm currently fixing shadow/shadow#423, but depending on how long that takes I might be able to see what's going on and fix this.
The text was updated successfully, but these errors were encountered: