https://issues.apache.org/bugzilla/show_bug.cgi?id=49456
--- Comment #1 from coheigea <cohei...@apache.org> 2010-06-17 11:53:18 EDT --- Thanks, I'll take a look. You may have missed my reply to your mail on the security-dev list (reproduced below): Hi Clement, I took a look at this issue after applying your patches for the other StorageResolver stuff. There's clearly an issue in StorageResolver, in that calling "next" returns the next object in the StorageResolverIterator, which is a StorageResolverSpi instance, not an X509Certificate. The solution here is to fix the StorageResolverIterator so that it iterates over both the "outer" and "inner" iterators looking for the next certificate. I also noticed that a few other StorageResolverSpi instances cache the iterator rather than create a new one each time, which is clearly a bug. I don't like the "hasNext()" and "next()" methods of StorageResolver. Instead the user should get the iterator and use that instead. I will make these changes, and create a patch in a new Bugzilla entry which you can review, if you'd like. Colm. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
