Channels
doorman
zercurity
infrastructure
code-review
queryhub
apple-silicon
carving
goquery
aws
querycon
golang
file-carving
fuzzing
help-proxy
darkbytes
process-auditing
general
windows
random
fleet-dev
tls
fim
awallaby
zentral
zeek
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
community-feeds
Powered by
#core
Title
# core
m
Mike Myers
03/31/2021, 1:42 AM
Should we change/fix the documentation, where it says osquery uses the system-provided OpenSSL?
https://github.com/osquery/osquery/blob/d80bb565349a6c99626b65b6e6cdbcf10ce0d5ee/docs/wiki/deployment/remote.md#server-testing
s
seph
03/31/2021, 3:40 AM
If it’s out of date, yes.
m
Mike Myers
03/31/2021, 3:08 PM
I don't believe we use system-provided libraries for anything since everything is statically linked. Was just confirming?
@Stefano Bonicatti
s
Stefano Bonicatti
03/31/2021, 3:09 PM
Yep, correct
🆒 1
Or I should say, correct for the typical definition of system provided libraries. We do use libc, libdl, librt, libpthread, libm from the system
That's the part that we cannot detach ourself from without changing the C library runtime
actually there's also a libz and libresolv
m
Mike Myers
03/31/2021, 4:07 PM
ah, yea, probably like on Windows you have to link to a couple of DLLs
6 Views
Post