You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2014/04/10 22:50:30 UTC
[jira] [Commented] (HADOOP-9856) Avoid Krb5LoginModule.logout issue
[ https://issues.apache.org/jira/browse/HADOOP-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965831#comment-13965831 ]
Jonathan Eagles commented on HADOOP-9856:
-----------------------------------------
Re-targeting to 2.5.0 as 0.23.x line is reaching maintenance mode.
> Avoid Krb5LoginModule.logout issue
> ----------------------------------
>
> Key: HADOOP-9856
> URL: https://issues.apache.org/jira/browse/HADOOP-9856
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: security
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HADOOP-9856.patch
>
>
> The kerberos login module's logout method arguably has a bug. {{Subject#getPrivateCredentials()}} returns a synchronized set. Iterating the set requires explicitly locking the set. The {{Krb5LoginModule#logout()}} is iterating and modifying the set w/o a lock. This may lead to a {{ConcurrentModificationException}} which is what lead to {{UGI.getCurrentUser()}} being unnecessarily synchronized.
--
This message was sent by Atlassian JIRA
(v6.2#6252)