On 9/12/23 03:01, Paolo Greppi wrote:
This may well be a doxygen bug, can anybody tell if there is any pattern?
I believe this is a deliberate behavior change in Doxygen 1.9.7, made to
address a problem affecting a different doxygen-to-RST converter:
https://github.com/doxygen/doxygen/pull
Candidate patch here:
https://github.com/krb5/krb5/pull/954
I think gss_krb5int_set_allowable_enctypes() should filter out invalid
enctypes, and only fail if no enctypes remain after filtering. The
current logic would also fail if the kernel supported an enctype which
libkrb5 did not (e.g. if the kernel gained support for the aes-sha2
enctypes, and someone
On Fri, 4 Jan 2019 19:24:52 -0500 Greg Hudson wrote:
> krb5_mcc_start_seq_get() is in the traceback, so the memory cache change
> is a clear candidate for the bug. I can't find anything wrong with the
> code, though. From the stack trace, there appears to be a memory ccache
>
On Fri, 04 Jan 2019 15:54:01 -0500 Sam Hartman wrote:
> There are no thread support changes between 1.16.1 and 1.16.2.
> There is one ccache related change which I'll include below related to
> memory ccaches.
> Do you know what type of credential cache is being used here?
krb5_mcc_start_seq_get
Here is the upstream master branch commit to work around this libc bug:
https://github.com/krb5/krb5/commit/65110210b75d38908cdd84cb202cf013ccf6ed0e
It will make its way onto the 1.14 branch and into a future 1.14 patch
release.
>From what I can tell, _LARGEFILE_SOURCE only seems to provide prototypes
for fseeko() and ftello(). I assume Sam means building such that off_t
is 64 bits, which I think requires defining _FILE_OFFSET_BITS=64.
off_t doesn't appear in any public krb5 header file, so there shouldn't
be any direct
This appears to be gnu libc bug 20251, which does not appear to have
been fixed yet:
https://sourceware.org/bugzilla/show_bug.cgi?id=20251
We will explore workarounds. I have opened a ticket in our database to
track the issue:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=8474
I do not understand the kernel behavior reflected in this trace
output. For fd 3 (principal.ok), we see:
fcntl64(3, F_OFD_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=6950411022381350912}) = -1 EINVAL (Invalid argument)
fcntl64(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_s
9 matches
Mail list logo
