You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2022. It is now read-only.
I noticed this morning that the utilization DaemonSet on the platform cluster is launching rsync on port 7999, exposing it directly to the Internet (hostNetwork: true). This is probably pretty innocuous because the default rsyncd configuration only allows access to configured modules from a subset of GCP IPv4 prefixes. Still, this is unnecessary and exposes a decade-old version of rsync (3.0.6: released May 8th, 2009) to the Internet.
The text was updated successfully, but these errors were encountered:
I noticed this morning that the utilization DaemonSet on the platform cluster is launching rsync on port 7999, exposing it directly to the Internet (hostNetwork: true). This is probably pretty innocuous because the default rsyncd configuration only allows access to configured modules from a subset of GCP IPv4 prefixes. Still, this is unnecessary and exposes a decade-old version of rsync (3.0.6: released May 8th, 2009) to the Internet.
The text was updated successfully, but these errors were encountered: