← 返回刚才阅读的位置

知识卡片

操作参考卡 · 4545.g.8.d.12

服务启用HTTPS仍需配置治理

理解等级:中级

ListenAndServeTLS在HTTP服务入口加载证书与私钥,使客户端使用https连接。启用入口TLS只是安全策略的一部分;若在代理终止TLS后明文跨主机转发,后段仍未加密。证书轮换、私钥权限和客户端信任都需要独立安排,不应把curl的insecure演示移作正常验收。

原稿入口形式:http.ListenAndServeTLS(":8080", "cert.pem", "key.pem", nil);调用者还应处理返回错误。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building a Cloud Native Service · 查看原书依据

      One way might be to put a reverse proxy in front of our service that can handle HTTPS requests and forward them to our key-value service as HTTP, but unless the two are co-located on the same server, we’re still sending unencrypted messages over a network. Plus, the additional service adds some architectural complexity that

    参考来源

    - 位置:《Cloud Native Go》第05章《Building a Cloud Native Service》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch05.xhtml) - 结论依据:ListenAndServeTLS在HTTP服务入口加载证书与私钥,使客户端使用https连接。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。 - 原始内容:One way might be to put a reverse proxy in front of our service that can handle HTTPS requests and forward them to our key-value service as HTTP, but unless the two are co-located on the same server, we’re still sending unencrypted messages over a network. Plus, the additional service adds some architectural complexity that