Difference between revisions of "Developing a preauth plugin"
From K5Wiki
(→Notes and Debugging Tips) |
(→Notes and Debugging Tips) |
||
| 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 [ |
+ | * Make use of [http://www.wireshark.org/ Wireshark] (terminal-based command is <code>tshark</code> for those without graphical environments) for examining network traffic. |
Revision as of 08:24, 5 May 2010
Recommended Reading
- Read RFC 4210
- Read
draft-ietf-krb-wg-preauth-framework(version 16 current as of 4/27/2010) - Read
src/include/krb5/preauth_plugin.h - Read
src/plugins/preauth/encrypted_challenge/*for a (tragically) comment-less implementation of a preauth plugin implemented using FAST - ghudson's quick flow overview at http://mailman.mit.edu/pipermail/krbdev/2010-April/008891.html
Pre-authentication Limitations
- 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
Notes and Debugging Tips
- Define
DEBUGas part of your build to tickle logging of more info in your KDC log file (proabablykrb5kdc.log). - Include
<syslog.h>, link againstkadm5<something>and make liberal use ofkrb5_klog_syslog - Testing a FAST factor preauth plugin such as
encrypted-challenge: http://mailman.mit.edu/pipermail/krbdev/2010-April/008935.html - Make use of
preferred_preauth_typesin the[libdefaults]section ofkrb5.conf - Make use of Wireshark (terminal-based command is
tsharkfor those without graphical environments) for examining network traffic.
