HTTP Public Key Pinning (HPKP) 透過 Public-Key-Pins 回應標頭,強制瀏覽器只接受特定公開金鑰簽發的憑證,防範偽造 CA 簽發惡意憑證。本文解析 SPKI 指紋原理、備份金鑰策略、三大主流 Web 伺服器設定範例與 Chrome 已知 Bug。
max-age:快取秒數(例 2592000 = 30 天)。includeSubDomains:延伸至子網域。pin-sha256="base64(SPKI指紋)":至少兩組(一主一備)。report-uri:違規回報端點。CA 可重新簽發同金鑰不同有效期的憑證,若釘選憑證雜湊會導致更新失敗。SPKI(SubjectPublicKeyInfo)包含演算法、參數與公開金鑰,金鑰不變即通過驗證。
openssl x509 -noout -in certificate.pem -pubkey |
openssl asn1parse -noout -inform pem -out public.key
openssl dgst -sha256 -binary public.key | openssl enc -base64
# 輸出範例:klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=
LoadModule headers_module modules/mod_headers.so
Header set Public-Key-Pins "pin-sha256=\"klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=\"; pin-sha256=\"633lt352PKRXbOwf4xSEa1M517scpD3l5f79xMD9r9Q=\"; max-age=2592000; includeSubDomains"
add_header Public-Key-Pins 'pin-sha256="klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY="; pin-sha256="633lt352PKRXbOwf4xSEa1M517scpD3l5f79xMD9r9Q="; max-age=2592000; includeSubDomains';
server.modules += ( "mod_setenv" )
$HTTP["scheme"] == "https" {
setenv.add-response-header = ( "Public-Key-Pins" => "pin-sha256=\"klO23nT2ehFDXCfx3eHTDRESMz3asj1muO+4aIdjiuY=\"; pin-sha256=\"633lt352PKRXbOwf4xSEa1M517scpD3l5f79xMD9r9Q=\"; max-age=2592000; includeSubDomains" )
}
加入 report-uri="https://example.com/hpkp-report",瀏覽器將以 JSON POST 發送違規資訊(含觀察到的指紋、預期指紋、URL、生效日期)。需自行建立接收端點解析入庫。
Chrome ≤ 38 將 max-age、includeSubDomains 視為共用,導致 HSTS/HPKP 設定互相覆蓋。詳見 Chromium Issue 444511。建議暫時對齊兩者參數,或待瀏覽器修復後再部署。
report-uri 監控違規嘗試。max-age 到期日,提前輪換金鑰。HPKP 能大幅提升 HTTPS 信任鏈強度,但操作風險較高(金鑰遺失將導致網站不可訪問),建議成熟團隊配合完整金鑰管理流程後再啟用。