zwass
fleetctl
on npm.
There's a fix for a low severity security vulnerability (https://github.com/fleetdm/fleet/security/advisories/GHSA-xwh8-9p3f-3x45) along with a sweet new host details page, live query error messages visible in the UI, and more. Check out the changelog (https://github.com/fleetdm/fleet/releases/tag/3.7.0) for full details.
<!here>benbass
02/03/2021, 6:02 PMbenbass
02/03/2021, 6:31 PMRyan
02/03/2021, 6:54 PMintermediate
from modern
it started working again.
server:
tls_compatibility: intermediate
zwass
intermediate
? Penny for your thoughts... We could change that default for the next Fleet release.benbass
02/03/2021, 7:15 PMEsteban
02/03/2021, 8:33 PMScott Lampert
02/03/2021, 9:25 PMdemonbhao
02/04/2021, 2:09 AMJerome
02/04/2021, 12:10 PMscutil
) and the one for NetBIOS.
The NetBIOS name is a dynamic name that can change regarding the connected network.
In our company, when a user is connected to our VPN, that NetBIOS name change and use the local IP adress, eg the name is ip-192-168-1-17.eu-west-1.compute.internal
.
In FleetUI, the hostname displayed is that name. I guess it comes from the field hostname
of table system_info
but for my usage I wanted to use the field local_hostname
or computer_name
. Is there a way to change this ? Otherwise I will open a feature request 🙂Artem
02/04/2021, 2:34 PMarod
02/04/2021, 7:42 PMRyan
02/05/2021, 11:36 AMChris Reisor
02/05/2021, 10:23 PMEsteban
02/08/2021, 2:57 PM{
"terminated": "listen tcp 0.0.0.0:443: bind: permission denied",
"ts": "2021-02-08T14:56:39.536145305Z"
}
Esteban
02/08/2021, 7:37 PMEsteban
02/08/2021, 8:34 PMIvan
02/10/2021, 2:01 PMEsteban
02/11/2021, 3:31 PMccombs
02/12/2021, 3:40 PMMike Hill
02/12/2021, 8:04 PMprepare db
returns migrations complete
but this continues to show in the logs. Any tips on how to resolve, please?zwass
fleetctl
-only release that includes fixes to the fleetctl preview
experience. Most folks in this channel will have no reason to upgrade.Mark Noonan
02/15/2021, 10:05 PMFeb 15 21:50:44 <ec2> systemd[1]: Started Kolide Fleet.
Feb 15 21:50:44 <ec2> fleet[10720]: Using config file: /etc/kolide/fleet.yml
Feb 15 21:50:44 <ec2> fleet[10720]: Error initializing datastore: register TLS config for mysql: register mysql tls config: key 'true' is reserved
Feb 15 21:50:44 <ec2?Feb 15 21:50:44 osquery-service-><http://ab251.ec2.vzbuilders.com|ab251.ec2.vzbuilders.com> systemd[1]: Unit fleet.service entered failed state.
Feb 15 21:50:44 <ec2> systemd[1]: fleet.service failed.
It looks like it hates the key true, however from the documentation:
mysql_tls_config
The tls value in a MYSQL DSN. Can be true,false,skip-verify or the CN value of the certificate.
Default value: none
Environment variable: FLEET_MYSQL_TLS_CONFIG
Config file format:
mysql:
tls_config: true
zwass
wtheaker
02/16/2021, 7:08 PMJocelyn Bothe
02/16/2021, 7:37 PMCollin
02/16/2021, 10:45 PMhilt
02/17/2021, 6:10 AMEsteban
02/17/2021, 1:22 PMsanjaykcse
02/18/2021, 5:55 PM[10:30 PM] LP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 6737.64
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.024e+06
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 57
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 7.098368e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.61130246694e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 7.47896832e+08
# HELP process_virtual_memory_max_bytes Maximum amount of virtual memory available in bytes.
# TYPE process_virtual_memory_max_bytes gauge
process_virtual_memory_max_bytes -1
# HELP promhttp_metric_handler_requests_in_flight Current number of scrapes being served.
# TYPE promhttp_metric_handler_requests_in_flight gauge
promhttp_metric_handler_requests_in_flight 1
# HELP promhttp_metric_handler_requests_total Total number of scrapes by HTTP status code.
# TYPE promhttp_metric_handler_requests_total counter
promhttp_metric_handler_requests_total{code="200"} 8
promhttp_metric_handler_requests_total{code="500"} 0
promhttp_metric_handler_requests_total{code="503"} 0
This information is available without logging to the fleet . Any suggestion , how to fix this . Is there any config option available to bar from revailing this information to attackers.