Channels
doorman
infrastructure
random
zercurity
community-feeds
fleet-dev
code-review
queryhub
apple-silicon
carving
tls
fim
goquery
zentral
aws
querycon
golang
zeek
file-carving
fuzzing
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
darkbytes
process-auditing
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
general
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
windows
Title
z
zwass
03/03/2021, 6:30 PMHi folks, looking for some input on handling "duplicate" host enrollment. Please check out the issue and comment there or here: https://github.com/fleetdm/fleet/issues/373
cc @nyanshak
n
nyanshak
03/03/2021, 6:32 PMI don't really have any problems with the proposal. I already use the 'host expiry' feature to age out MIA hosts (which is super useful with ephemeral hosts).
Implementing the proposal would be an excellent solution for my use case 🤷♀️
Osquery provides the full contents of the^ Is there a minimum version of osquery where that started happening or has this been the behavior with osquery tls enrollment forever? (try to keep up to date, but just want to make sure this assumption always holds)table in each enrollment requestosquery_info
d
defensivedepth
03/03/2021, 6:42 PMThe proposed solution looks good to me.
s
seph
03/04/2021, 5:33 AMPretty sure the enrollment info has been there for years.
The fancy thing is to make this an option somewhere, but increasing fleet configuration options has other tradeoffs.