miner

Hi @sylvainOL , Sorry for the late response. As you can see that the `values.yaml` file configuration is a template that keep consistent with upstream goharbor repository. It use `5s`...

> Will this PR come into Harbor any time soon? Because Harbor's unsecured redis server is reported by security tools. We would like to know what these security tools are...

True, thanks for your follow-up elaboration! We will have a discuss on this and evaluate the risk with my colleague soon.

We have a discussion with security team. And they agree with the risk described above by @mfriess2. We probably consider to set this password configuration for internal Redis server as...

Hi @freebased, This install process can be conducted by not only root user (`$EUID eq 0`), but also by the users who has root permissions, for example `sudo ./install.sh`. So...

it would open for discussion here https://github.com/goharbor/harbor/discussions/17400

Hi @fgierlinger Sorry I can't reproduce this problem. I am using `harbor version: v2.4.1` with docker engine version `0.10.12`, and I can login using the password with a dollar sign...

Hi @balonik, Thanks for your contribution. It seems like if we change the `disabled` into `deactivate`, we not only need to change the `configs.py` file, but also have to care...

Hi @balonik , I think the `deactivate` setting should consistent with docker registry configuration which is using `disable` for redirect option https://docs.docker.com/registry/configuration/#list-of-configuration-options. Actually we may intend to using `disable` at...

> @MinerYang I have changed it back to `disable` including the Jinja template. Sorry for a delay in getting the reply. And here's some adjustments we need to make based...