We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在群里给大佬提过了,如果忙不过来,首先加最简单的安全机制即可,
在服务端和客户端的配置文件里加上key参数,客户端请求时对比即可,代码可能就几行。这是用很小的代码量拦截了大部分的黑客攻击操作。
参考redis,前车之鉴,大部分只在内网运行,一样被黑客打成筛子,往往还会成为突破口。 大部分时间运行在内网并不能表示可以忽略安全性。
客户端和服务端都配置key参数,客户端请求时比较key,不正确就拒绝连接,正确才允许继续
No response
The text was updated successfully, but these errors were encountered:
简单点的,就走 Basic Auth 稍微处理下,回头有空了可以搞下,ssl 的短期内不搞,没时间精力
Sorry, something went wrong.
稍微搞了下,多用户管理,密码验证, known hosts 检测什么的,基础认证逻辑做了一套,局域网应该基本够用了。。
No branches or pull requests
你在什么场景下需要该功能?
在群里给大佬提过了,如果忙不过来,首先加最简单的安全机制即可,
在服务端和客户端的配置文件里加上key参数,客户端请求时对比即可,代码可能就几行。这是用很小的代码量拦截了大部分的黑客攻击操作。
参考redis,前车之鉴,大部分只在内网运行,一样被黑客打成筛子,往往还会成为突破口。
大部分时间运行在内网并不能表示可以忽略安全性。
描述可能的解决方案
客户端和服务端都配置key参数,客户端请求时比较key,不正确就拒绝连接,正确才允许继续
描述你认为的候选方案
No response
其他信息
No response
The text was updated successfully, but these errors were encountered: