Developing a preauth plugin - Revision history

MattCrawford: RFC number wrong: 4210 s/b 4120 /* Recommended Reading */

2011-06-07T19:37:28Z

RFC number wrong: 4210 s/b 4120 ‎Recommended Reading

2010-05-05T13:31:44Z

‎Pre-authentication Limitations

2010-05-05T13:28:09Z

‎Pre-authentication Limitations

2010-05-05T13:27:33Z

‎Pre-authentication Limitations

2010-05-05T13:24:48Z

‎Notes and Debugging Tips

2010-05-05T13:22:20Z

‎Notes and Debugging Tips

2010-04-30T16:44:45Z

‎Notes and Debugging Tips

2010-04-30T16:44:15Z

‎Notes and Debugging Tips

2010-04-30T16:34:33Z

‎Debugging Tips

2010-04-30T16:30:38Z

‎Debugging Tips

@@ Line 1: / Line 1: @@
 == Recommended Reading ==
-* Read RFC 4210
+* Read RFC 4120
 * Read <code>draft-ietf-krb-wg-preauth-framework</code> (version 16 current as of 4/27/2010)
 * Read <code>src/include/krb5/preauth_plugin.h</code>

← Older revision		Revision as of 13:31, 5 May 2010
Line 11:		Line 11:
	* FAST-based preauth (see <code>draft-ietf-krb-wg-preauth-framework</code>) support is largely unimplemented from a practical usage perspective at this point.		* FAST-based preauth (see <code>draft-ietf-krb-wg-preauth-framework</code>) support is largely unimplemented from a practical usage perspective at this point.

⚫	~~References for above:~~ http://mailman.mit.edu/pipermail/krbdev/2010-April/008902.html
		+	krbdev thread References for above:
		⚫	* http://mailman.mit.edu/pipermail/krbdev/2010-April/008902.html
		+	* http://mailman.mit.edu/pipermail/krbdev/2010-April/008933.html

	== Notes and Debugging Tips ==		== Notes and Debugging Tips ==

@@ Line 9: / Line 9: @@
 * There is no way to require that a certain preauth method is used.
 * Likewise, there is also no way to indicate a preferred preauth flow (method A, then B, then C).
-* FAST-based preauth support is largely unimplemented from a practical usage perspective at this point.
+* FAST-based preauth (see <code>draft-ietf-krb-wg-preauth-framework</code>) support is largely unimplemented from a practical usage perspective at this point.
 References for above: http://mailman.mit.edu/pipermail/krbdev/2010-April/008902.html

@@ Line 9: / Line 9: @@
 * There is no way to require that a certain preauth method is used.
 * Likewise, there is also no way to indicate a preferred preauth flow (method A, then B, then C).
 References for above: http://mailman.mit.edu/pipermail/krbdev/2010-April/008902.html

@@ Line 17: / Line 17: @@
 * Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html
 * Make use of <code>preferred_preauth_types</code> in the <code>[libdefaults]</code> section of <code>krb5.conf</code>
-* Make use of [Wireshark | http://www.wireshark.org/] (terminal-based command is <code>tshark</code> for those without graphical environments) for examining network traffic.
+* Make use of [http://www.wireshark.org/ Wireshark] (terminal-based command is <code>tshark</code> for those without graphical environments) for examining network traffic.

← Older revision		Revision as of 13:22, 5 May 2010
Line 17:		Line 17:
	* Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html		* Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html
	* Make use of <code>preferred_preauth_types</code> in the <code>[libdefaults]</code> section of <code>krb5.conf</code>		* Make use of <code>preferred_preauth_types</code> in the <code>[libdefaults]</code> section of <code>krb5.conf</code>
		+	* Make use of [Wireshark \| http://www.wireshark.org/] (terminal-based command is <code>tshark</code> for those without graphical environments) for examining network traffic.

@@ Line 16: / Line 16: @@
 * Include <code><syslog.h></code>, link against <code>kadm5<something></code> and make liberal use of <code>krb5_klog_syslog</code>
 * Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html
-* Make use of <code>preferred_preauth_types</code> in <code>krb5.conf</code>'s <code>[libdefaults]</code>
+* Make use of <code>preferred_preauth_types</code> in the <code>[libdefaults]</code> section of <code>krb5.conf</code>

← Older revision		Revision as of 16:44, 30 April 2010
Line 16:		Line 16:
	* Include <code><syslog.h></code>, link against <code>kadm5<something></code> and make liberal use of <code>krb5_klog_syslog</code>		* Include <code><syslog.h></code>, link against <code>kadm5<something></code> and make liberal use of <code>krb5_klog_syslog</code>
	* Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html		* Testing a FAST factor preauth plugin such as <code>encrypted-challenge</code> : http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html
		+	* Make use of <code>preferred_preauth_types</code> in <code>krb5.conf</code>'s <code>[libdefaults]</code>

@@ Line 12: / Line 12: @@
 References for above: http://mailman.mit.edu/pipermail/krbdev/2010-April/008902.html
-== Debugging Tips ==
+== Notes and Debugging Tips ==
 * Define <code>DEBUG</code> as part of your build to tickle logging of more info in your KDC log file (proabably <code>krb5kdc.log</code>).
 * Include <code><syslog.h></code>, link against <code>kadm5<something></code> and make liberal use of <code>krb5_klog_syslog</code>