summaryrefslogtreecommitdiffstats
path: root/src/mac
diff options
context:
space:
mode:
authorGeoffrey King <gjking@mit.edu>1998-08-19 11:06:25 +0000
committerGeoffrey King <gjking@mit.edu>1998-08-19 11:06:25 +0000
commitbd86dea69d96583f2a73a8519cfaca61fb61289c (patch)
treea738d56bd9b46f38b7b8f41ebfd285c380f7ed8a /src/mac
parentbfef7c4a32306a55fcc20647c1bd479954de13d4 (diff)
downloadkrb5-bd86dea69d96583f2a73a8519cfaca61fb61289c.tar.gz
krb5-bd86dea69d96583f2a73a8519cfaca61fb61289c.tar.xz
krb5-bd86dea69d96583f2a73a8519cfaca61fb61289c.zip
Add optional support for the CCC (Clear Command Channel) command.
This command is dangerous, since it allows commands to be transmitted without integrity checking, so the default behavior without the -c option is still for the server to refuse to accept unprotected commands. * ftpd.c: Add a new command line option, -c, which tells the server to accept the CCC command. * ftpcmd.y: If the -c option was given, check to make sure the CCC command itself was integrity protected, and then set ccc_ok to allow future commands to be transmitted as cleartext. (getline): Now that CCC is potentially allowed, we must check to see if we are parsing an unprotected command even if a security context is established (i.e. auth_type is set). git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@10846 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/mac')
0 files changed, 0 insertions, 0 deletions