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
#kolide
Title
# kolide
j
Jose
04/22/2020, 4:07 PM
Hi I'm trying to connect Osquery on (windows 10) to my fleet on (ubuntu 18) but I'm getting this error ( tls handshake error ) any ideas ?
#kolide
e
Erich Stoekl
04/22/2020, 10:50 PM
Sounds like your TLS cert on the windows 10 osquery box does not match the one your Fleet server is using.
So your fleet server is set up with .crt and .key files. Make sure your osquery agents are also using that same .crt file.
See:
https://osquery.readthedocs.io/en/stable/deployment/remote/#tls-client-auth-enrollment
j
Jose
04/23/2020, 7:16 AM
@Erich Stoekl
I took the .pem file + enrollment key from the server and put them in the osquery file
e
Erich Stoekl
04/23/2020, 9:18 PM
the osquery agent needs a cert, not a private key. can you put the crt file on the osquery agent?
j
Jose
04/23/2020, 9:25 PM
@Erich Stoekl
Actually it just worked with the private key.
😮 1
e
Erich Stoekl
04/23/2020, 9:26 PM
If that's sufficient for you, great. I wouldn't recommend storing the private key on the osquery agents though.
👍 1
2 Views
Post