logo_kerberos.gif

Search results

From K5Wiki
Jump to: navigation, search
  • | Upgrading a Kerberos infrastructure (order, backward compatibility) || || || ||
    20 KB (3,209 words) - 14:28, 5 June 2013
  • ...s. Even if this particular project isn't working we could use QA, testing infrastructure, new services (eg: OpenGrok), etc.
    5 KB (811 words) - 21:36, 10 January 2011
  • ...ducts. Organizations that currently use Kerberos as a key element of their infrastructure wish to take advantage of its unique benefits while moving to Web-based sys ...ards a more cohesive and widely deployed Kerberos-based Web authentication infrastructure.
    99 KB (14,634 words) - 23:15, 29 October 2008
  • infrastructure lower infrastructure costs
    6 KB (835 words) - 21:37, 22 August 2008
  • *** How to use the Coverity infrastructure
    2 KB (379 words) - 21:42, 10 January 2011
  • * (Some discussion of the limitations of our testing infrastructure)
    2 KB (315 words) - 03:57, 4 January 2011
  • The trace logging infrastructure has been implemented for 1.9. Trace events have been added for:
    5 KB (759 words) - 17:23, 12 October 2010
  • == Infrastructure ==
    12 KB (1,826 words) - 23:24, 14 October 2011
  • Pkinit requires a public key infrastructure. The simplest use of
    10 KB (1,462 words) - 01:32, 9 October 2013
  • ==Current support infrastructure==
    22 KB (3,322 words) - 18:57, 3 August 2010
  • ...f equal-priority SRV records, so randomization of SRV responses by the DNS infrastructure would be necessary for load-balancing to occur, and such randomization is s
    6 KB (1,080 words) - 15:54, 1 October 2010
  • * The KDC may require X.509 PKI infrastructure on the Kerberos certificate (for instance, to enforce a federation). ...ot be formulated before has been the lack of a reliable, as in secure, DNS infrastructure. With the advent of DNSSEC, this is now very well possible.
    10 KB (1,584 words) - 11:08, 14 February 2018
  • === Current support infrastructure ===
    25 KB (3,739 words) - 04:54, 27 June 2012
  • The goal of the project is to create an infrastructure and process for the future development of the extensive Kerberos documenta
    3 KB (462 words) - 15:21, 29 October 2013
  • ;Tom: If you don't have git hosting infrastructure, it could be useful to register for Github.
    983 B (153 words) - 19:32, 18 March 2011
  • * Kernel / user split (for NFS, etc.): Add build infrastructure demonstrating and testing a message-processing subset of the gss-krb5 mecha * Localization: Create infrastructure for localization of client user interface messages using gettext.
    2 KB (255 words) - 21:55, 27 January 2012
  • ;Tom: Looking at buildbot. (Testing infrastructure is partially shut down due to office moves.) Buildbot has some security iss
    825 B (122 words) - 22:06, 13 May 2011
  • The purpose of this project is to create build infrastructure to help identify and preserve the independence of the necessary code subset
    3 KB (466 words) - 22:10, 7 August 2012
  • The purpose of this project is to add infrastructure for localization of user interface messages in the krb5 tree, using gettext ===Basic infrastructure===
    4 KB (608 words) - 21:49, 12 October 2011
  • ;Will: Would be nice to have a generic infrastructure.
    1 KB (227 words) - 21:47, 12 March 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Views
Personal tools