https://github.com/osquery/osquery logo
#kolide
Title
# kolide
j

jrossi

07/25/2018, 5:40 PM
@groob I built launcher from master. This makes sense let me do get this compiled asap
g

groob

07/25/2018, 5:41 PM
sounds good. flag me if anything I’ll folow up
j

jrossi

07/25/2018, 5:47 PM
I don't see a tag/branch for stable: https://github.com/kolide/launcher/tree/master
there’s a compiled binary in the zip too if that helps
j

jrossi

07/25/2018, 5:52 PM
launcher - version 0.5.0 branch: master revision: 6f697beacb9e530a97376c9eed45c9013564e946 build date: 2018-02-28T192056Z build user: victor go version: go1.10
Turns out that is the one I am using
g

groob

07/25/2018, 5:53 PM
heh ok
lets look at the server then
do you see any logs in fleet that log launcher connecting?
also would be curious to see the output of
curl -v --http2 <https://fleet.acme.co>
actually that might not do anything.there’s a header there too
j

jrossi

07/25/2018, 5:55 PM
redhat 😞 curl is old
does not support http2
g

groob

07/25/2018, 5:56 PM
here we go
Copy code
curl -v --header "Content-Type: application/grpc" --http2
ah. curl from a mac?
or from a recent docker image
j

jrossi

07/25/2018, 5:57 PM
that is what I am doing now
g

groob

07/25/2018, 5:58 PM
somewhat offtopic, but curious what problem you’re looking to solve with launcher, vs just deploying osquery natively
(I usually ask because there’s a few primary reasons people are looking into it)
if curl doesnt help demystify things, i wrote a tiny utility for someone in another issue https://github.com/kolide/fleet/issues/1650#issuecomment-347358980
2 Views