Hi,
thanks for the previous response, marc.
ok, here's the sequences. Note that these are re-typed, not captured:
The following occurs when the CCC command is *not* attempted.
220 blah FTP server (Version 5.60) ready
AUTH GSSAPI
334 Using authentication type GSSAPI; ADAT must follow
ADAT Y
[EMAIL PROTECTED] ("Glen Matthews") writes:
>> thanks for your response, marc. actually, i *am* implementing the full
>> spec, all (except for ccc?) of which is working - CCC is just an option
>> (which we will deprecate and warn people about). or at least i think i am -
>> rfc 2228. i don't se
ED]]On Behalf Of
Marc Horowitz
Sent: Thursday, April 11, 2002 6:48 PM
To: [EMAIL PROTECTED]
Subject: Re: gssapi and CCC command
I haven't looked at the MIT code in a long time, but I just took a
quick glance, and it looks like either the username is invalid, or the
initial password request fail
I haven't looked at the MIT code in a long time, but I just took a
quick glance, and it looks like either the username is invalid, or the
initial password request fails. If you can look at the kdc logs, find
out if the AS-REQ is really succeeding.
I also have to mention that using CCC isn't a ve
Hi,
i'm writing an ftp client using the gssapi with kerberos, and am somewhat
puzzled by the CCC command behaviour.
basically, when i enable clear channel commands using CCC, it is accepted
with a 200-level message. i can enter various commands (notably PBSZ, PROT -
these seem to work ok). h
