summaryrefslogtreecommitdiffstats
path: root/src/lib/kadm5
diff options
context:
space:
mode:
authorSam Hartman <hartmans@mit.edu>2009-01-03 23:20:35 +0000
committerSam Hartman <hartmans@mit.edu>2009-01-03 23:20:35 +0000
commit02351224e88fa4fa560a8a6073664cbcdfd73b62 (patch)
tree32264f8643d576247d92ea249e2dfd25493385a8 /src/lib/kadm5
parent5bfe3caf46dcc046b66066421ee0a9e9fbc076e3 (diff)
downloadkrb5-02351224e88fa4fa560a8a6073664cbcdfd73b62.tar.gz
krb5-02351224e88fa4fa560a8a6073664cbcdfd73b62.tar.xz
krb5-02351224e88fa4fa560a8a6073664cbcdfd73b62.zip
Remove support for setting a client flag indicating pkinit is used on the db entry.
I'm reasonably sure that this would belong in a pkinit plugin not in do_as_req.c. Also, the flag should be documented to indicate what it means--client attempted pkinit? Client succeeded in using pkinit? I also wonder whether you want a mechanism for a db plugin to figure out all the padata or fast factors that a request is using. Note that this flag will need to be added back by at least one vendor. git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@21694 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/lib/kadm5')
0 files changed, 0 insertions, 0 deletions