Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'heimdal'

This is an experimental report containing PRs for tag 'heimdal' as of 4-18-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'heimdal':
SSubmittedTrackerResp.Description
o2013/10/01kern/182546stas[heimdal] [patch] base heimdal build error if WITH_OPENLDAP is defined
o2011/04/07kern/156245[heimdal] [patch] heimdal 1.1 broken in 8-stable and 8-release as far as gssapi_krb5 is concerned
o2011/02/12kern/154709[heimdal] Kerberos V5 refuses authentication because Read req failed: ASN.1 encoding ended unexpectedly [regression]
o2009/05/16bin/134569[heimdal] krb5-config(1) does not return all libs necessary when linking admin servers
o2007/11/06kern/117867[heimdal] kinit generates bad tickets on multihomed IPv6 hosts - may need to update krb
5 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.