user
07/01/2022, 5:47 PMSaulo Guilhermino
07/04/2022, 7:47 PMgoquery
within `fleetctl`:
.connect: ScheduleQueryAndWait call failed: upgrade live query result websocket: websocket: bad handshake
I assume this is related to our infrastructure security controls regarding websocket routes. In my deployment I have to specify which routes are websockets (currently only /api/v1/fleet/results
). So my real question is, what routes do I need to allow for Goquery to work properly? (If the issue is about that)defensivedepth
07/05/2022, 11:22 PMComplex passwords
(ie requiring mixed character types) as a security best practice has been deprecated in favor of minimum password length (as well as a few other controls) by NIST (see section 5.1.1.2 Memorized Secret Verifiers) and the wider InfoSec community for a few years now - and I would like to tweak the complexity requirements for my deployments to be more inline with this.Lucas Santos
07/06/2022, 1:22 PMAdam Connor
07/07/2022, 1:39 AMGET /api/v1/fleet/queries
I’m actually receiving this response-
{
"queries": []
}
I’m not sure how to troubleshoot this, any hints please?Rafael
07/07/2022, 1:53 PMuser
07/07/2022, 3:10 PMAntony Rivera
07/07/2022, 6:06 PMJason
07/07/2022, 6:39 PMDaniel Cross
07/08/2022, 12:54 AMzwass
Angelo
07/10/2022, 10:49 PMteam's enroll_secret
to installer? I’m looking for a way that can be done automatically without manually running again fleetctl package
with the team's enroll_secret
.
I thought about having a universal installer WITHOUT enroll_secret. During the installation, it will ask Fleet server or one of our servers for the device’s actual team enroll_secret. Will that work? Any other better approaches?Ryan
07/11/2022, 2:44 PMAlex Mitchell
07/11/2022, 4:01 PMSaulo Guilhermino
07/11/2022, 5:31 PMnick fury
07/11/2022, 5:35 PMTarek Talaat
07/11/2022, 6:54 PMRyan
07/12/2022, 12:55 PMThere was an error with single sign-on. Please contact your Fleet administrator.
The journalctl
logs show:
fleet[4403]: level=error ts=2022-07-12T12:55:25.527528789Z component=http user=unauthenticated method=POST uri=/api/v1/fleet/sso/callback took=3.385322ms err="response validation failed: wrong audience:fleet"
Ari Weinberg
07/12/2022, 2:19 PMJoe
07/12/2022, 3:35 PMGabe Hernandez
07/12/2022, 5:22 PMuser
07/12/2022, 8:03 PMAri Weinberg
07/12/2022, 8:45 PM{
"component": "http",
"err": "error in query ingestion",
"ingestion-err": "campaign waiting for listener (please retry)",
"ip_addr": "ENDPOINT-IP:41730",
"level": "error",
"method": "POST",
"took": "1.136788ms",
"ts": "2022-07-12T20:38:50.060101107Z",
"uri": "/api/v1/osquery/distributed/write",
"x_for_ip_addr": ""
}
Also getting (although not sure its related):
{
"component": "http",
"err": "read auth token: reading from websocket: sockjs: session not in open state",
"msg": "failed to read auth token",
"ts": "2022-07-12T20:37:57.77330272Z"
}
The problem appears to be the agent talking back to the fleet server, because I can see the query being run on the agent in debug mode. It just seems to fail when posting back the results. Agent is vanilla OSquery 5.1.0
This only started since I updated a few minutes ago from fleet 4.9.1Kathy Satterlee
07/12/2022, 8:52 PMAri Weinberg
07/12/2022, 9:13 PMJay
07/12/2022, 9:53 PMJay
07/12/2022, 10:26 PMStephan M
07/13/2022, 2:13 AMducna09
07/13/2022, 8:57 AMJay
07/13/2022, 9:56 AM