[
https://issues.apache.org/jira/browse/HADOOP-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-5364:
----------------------------------
Status: Open (was: Patch Available)
* The StringBuffer in HsftpFileSystem need not be built unless the certificate
is expired.
* Use System.currentTimeMillis instead of creating a new Date object and
calling getTime
* In ProxyUtil, "No Server certs was found" should be "No server certificates
were found"
* This will warn for every open/list operation in HsftpFileSystem if a
certificate is expired? This seems excessive, particularly since checksum
verification will generate at least two messages for each file. So this remains
usable if the certificate is within the limit, consider making the 30 day
check/warning configurable and disable it if it is 0. Is a warning for every
request a requirement?
> Adding SSL certificate expiration warning to hdfsproxy
> ------------------------------------------------------
>
> Key: HADOOP-5364
> URL: https://issues.apache.org/jira/browse/HADOOP-5364
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hdfsproxy
> Reporter: Kan Zhang
> Assignee: zhiyong zhang
> Attachments: HADOOP-5364.patch, HADOOP-5364.patch, HADOOP-5364.patch,
> HADOOP-5364.patch
>
>
> SSL certificate warning should be provided on both client and proxy server
> side.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
