[ 
https://issues.apache.org/jira/browse/TS-3216?focusedWorklogId=29883&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29883
 ]

ASF GitHub Bot logged work on TS-3216:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Sep/16 01:59
            Start Date: 28/Sep/16 01:59
    Worklog Time Spent: 10m 
      Work Description: Github user masaori335 commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/990#discussion_r80831720
  
    --- Diff: iocore/net/SSLUtils.cc ---
    @@ -1895,10 +1963,17 @@ ssl_store_ssl_context(const SSLConfigParams 
*params, SSLCertLookup *lookup, cons
         keyblock = ssl_context_enable_tickets(ctx, NULL);
       }
     
    +  // Generate HPKP header if hpkp is enabled.
    +  if (sslMultCertSettings.hpkp_enabled >= 0 ? 
sslMultCertSettings.hpkp_enabled : params->hpkp_enabled) {
    +    hpkp = ssl_context_enable_hpkp(params, sslMultCertSettings);
    --- End diff --
    
    It looks like `SSLInitServerContext` doesn't handle SSLCertContext. What 
I'm missing?


Issue Time Tracking
-------------------

    Worklog Id:     (was: 29883)
    Time Spent: 4h 40m  (was: 4.5h)

> Add HPKP (Public Key Pinning Extension for HTTP) support
> --------------------------------------------------------
>
>                 Key: TS-3216
>                 URL: https://issues.apache.org/jira/browse/TS-3216
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: SSL
>            Reporter: Masaori Koshiba
>            Assignee: Masaori Koshiba
>              Labels: review
>             Fix For: 7.1.0
>
>         Attachments: hpkp-001.patch, hpkp-002.patch, hpkp-003.patch
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> Add "Public Key Pinning Extension for HTTP" Support in Traffic Server.
> RFC 7469 Public Key Pinning Extension for HTTP
> - https://tools.ietf.org/html/rfc7469



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to