Zach Wasserman

Thanks for contributing this, and apologies for the delay in review. I'd like to get user deletion merged, but I am concerned about using soft-deletion as the strategy. Ideally I'd...

We can revisit this now that #2327 has been merged.

This is something that has been brought up in the past and determined that the UX is worth it for the possible enumeration. If additional folks think this ought to...

The tradeoff is this: Downside - User enumeration is possible. Upside - Legitimate users can get some information to help them understand why their login failed. For folks who are...

There's no way to do this without making code changes. You might be able to do it by removing the `authenticatedUser` middleware in https://github.com/kolide/fleet/blob/master/server/service/handler.go#L137, but this would break things in...

My recommendation for this would be to use something like Logstash to pull the logs from S3 and split them by query. We could look into supporting Kinesis Streams in...

This does not look like an error on the Fleet side. Notice the error message: rpc error: code = Internal desc = grpc: **error while marshaling**: proto: field \"kolide.agent.LogCollection.Log.Data\" contains...

Either escape it in some way, or drop the invalid characters I suppose. Probably best to do this only after receiving the error so we don't add an extra encoding/scanning...

@B3DTech FWIW we (github.com/fleetdm) are working on an osquery autoupdater that takes a different approach by letting osquery do the heavy lifting. This (I believe) will help resolve issues like...

This is a very interesting problem... When Fleet runs a query, it runs that query on each targeted host and provides the union of the results from those hosts. There's...