Security Feature Request and Issues

未指定任何文件或测试。首先定位 FAQ 条目和配置文件创建路径，然后确定所请求的安全问题中哪些属于范围之内。完成后应明确登录速率限制的行为，并处理配置文件的暴露问题；任何自定义或 fail2ban 工作都应单独定义。

Issue 1: Ambiguity in Login Rate Limits

The code-server FAQ states:

code-server supports setting a single password and limits logins to two per minute plus an additional twelve per hour.

This language is somewhat ambiguous and leaves room for interpretation. For example:

1. Are successful logins also part of the rate limit?
2. Are failed logins excluded from the rate limit?

Proposed Solution

To clarify, the FAQ could be revised as follows:

code-server supports setting a single password and limits all logins (successful or unsuccessful) to two per minute plus an additional twelve per hour.

Issue 2: Configuration File Permissions

When starting code-server, the generated configuration file is created with permissions that allow other users on the system to view the file. This can potentially expose the user’s password.

Proposed Solution

• Ensure that the configuration file is created with stricter permissions, making it readable and writable only by the user running code-server.
• Alternatively, provide a clear warning in the documentation about this behavior so users can manually adjust permissions.

Additional Feature Suggestion

As someone who prioritizes tight security but does not want to limit successful logins, it would be ideal to:

• Customize rate limit settings.
• Configure integration with fail2ban for more comprehensive security.

These enhancements would provide significant benefits for users who require fine-grained control over security policies.