2008/9/11 Peter Shoults :
> Henrik wrote:
>> or is the issues fixed in some other way ?
>> --
>>
>
> Yes - it is fixed a different way. The key CR that you need to know about
> is CR 1085341. This fixed the fopen issue in opensolaris as well as in
> Solaris 10. What it did is add new functionali
On Thu, Sep 11, 2008 at 07:31:05PM -0400, Ken Raeburn wrote:
> I don't think the fopen option is in the Solaris 10 systems we're
> running in my group -- at least, not in the man pages. Does fileno()
> still work when this option is used? If not, how would I set close-on-
> exec? Does fdope
On Sep 11, 2008, at 16:51, Henrik Lynggaard wrote:
> Is this fix something that will make its way into the MIT kerberos ? I
> have tried goggling for any backport/upstream fix, but found nothing
> so far
I don't think we have any patches floating around, but I've made a
note in the bug database
???Was just doing some testing going through the different kinit and
PKCS11 opts to make sure everything is working ok. One of the options
which can be given as an argument is a path to a libpkcs11 library to
use (for e.g. -X PKCS11:module_name=/tmp/libpkcs11.so.1).
kinit is already linked against
On Thu, Sep 11, 2008 at 04:40:19PM -0500, Douglas E. Engert wrote:
>
>
> Nicolas Williams wrote:
> > On Thu, Sep 11, 2008 at 03:35:47PM -0500, Nicolas Williams wrote:
> >> On Thu, Sep 11, 2008 at 03:11:15PM -0500, Will Fiveash wrote:
> >>> If we must support "-X PKCS11:module_name=/tmp/libpkcs11.
On Thu, Sep 11, 2008 at 04:40:19PM -0500, Douglas E. Engert wrote:
> Nicolas Williams wrote:
> >On Thu, Sep 11, 2008 at 03:35:47PM -0500, Nicolas Williams wrote:
> >>On Thu, Sep 11, 2008 at 03:11:15PM -0500, Will Fiveash wrote:
> >>>If we must support "-X PKCS11:module_name=/tmp/libpkcs11.so.1" the
Nicolas Williams wrote:
> On Thu, Sep 11, 2008 at 03:35:47PM -0500, Nicolas Williams wrote:
>> On Thu, Sep 11, 2008 at 03:11:15PM -0500, Will Fiveash wrote:
>>> If we must support "-X PKCS11:module_name=/tmp/libpkcs11.so.1" then this
>
> If we can make OpenSC accessible through libpkcs11 (and I
Will Fiveash wrote:
> On Thu, Sep 11, 2008 at 11:45:35AM -0500, Nicolas Williams wrote:
>> On Thu, Sep 11, 2008 at 06:26:40PM +0200, Mark Phalan wrote:
>>> ???Was just doing some testing going through the different kinit and
>>> PKCS11 opts to make sure everything is working ok. One of the option
On Thu, Sep 11, 2008 at 03:35:47PM -0500, Nicolas Williams wrote:
> On Thu, Sep 11, 2008 at 03:11:15PM -0500, Will Fiveash wrote:
> > If we must support "-X PKCS11:module_name=/tmp/libpkcs11.so.1" then this
If we can make OpenSC accessible through libpkcs11 (and I don't see why
not, though the fac
On Thu, Sep 11, 2008 at 03:11:15PM -0500, Will Fiveash wrote:
> > Can we exclude that option in Solaris? OTOH, if we package and deliver
> > OpenSC then we arguably should not exclude that option, but make it
> > work instead.
>
> Perhaps I'm off base here but wouldn't it be better to add whateve
On Thu, Sep 11, 2008 at 11:45:35AM -0500, Nicolas Williams wrote:
> On Thu, Sep 11, 2008 at 06:26:40PM +0200, Mark Phalan wrote:
> > ???Was just doing some testing going through the different kinit and
> > PKCS11 opts to make sure everything is working ok. One of the options
> > which can be given
One more comment: The OpenSC pkcs11 libs are called opensc-pkcs11.so,
onepin-opensc-pkcs11.so and pkcs11-spy.so
Mark Phalan wrote:
> ???Was just doing some testing going through the different kinit and
> PKCS11 opts to make sure everything is working ok. One of the options
> which can be given as
On Thu, Sep 11, 2008 at 01:15:08PM -0500, Douglas E. Engert wrote:
> >Can we exclude that option in Solaris? OTOH, if we package and deliver
> >OpenSC then we arguably should not exclude that option, but make it
> >work instead.
>
> Yes!
Yes, I think that's the right approach.
> >The two option
Nicolas Williams wrote:
> On Thu, Sep 11, 2008 at 06:26:40PM +0200, Mark Phalan wrote:
>> ???Was just doing some testing going through the different kinit and
>> PKCS11 opts to make sure everything is working ok. One of the options
>> which can be given as an argument is a path to a libpkcs11 lib
On Thu, Sep 11, 2008 at 10:55:58AM -0700, Henry B. Hotz wrote:
> Don't forget that OpenSC has a pkcs11-spy library that might be nice
> to allow for debugging. I'd like to preserve the option for that
> reason, if nothing else. It would seem to get you into all the
> interposition issues th
On Thu, Sep 11, 2008 at 06:26:40PM +0200, Mark Phalan wrote:
> ???Was just doing some testing going through the different kinit and
> PKCS11 opts to make sure everything is working ok. One of the options
> which can be given as an argument is a path to a libpkcs11 library to
> use (for e.g. -X PKCS
Henrik wrote:
> Hi
>
> I have found these two bug reports regarding the fopen usage which both have
> the status fix-delivered.
>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6221296
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6234782
>
yes it appears the fix is
Don't forget that OpenSC has a pkcs11-spy library that might be nice
to allow for debugging. I'd like to preserve the option for that
reason, if nothing else. It would seem to get you into all the
interposition issues that libumem has, and I can't tell you how to
solve those. |-P
On Sep
Hi
I have found these two bug reports regarding the fopen usage which both have
the status fix-delivered.
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6221296
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6234782
however when I browse the source code using the source
19 matches
Mail list logo
