Mohtalim

how do you ftp the contents of directory structures? like, i have a directory with 300 subdirectories, and when i

mput *

it puts all the files in the top directory, but doesn't copy over the subdirectories or their contents. I tried

mput */*

but it said "Arguments too long."

any thoughts?

If you can, use a non-cmdline ftp client, like FlashFXP

btw, I recommend you avoid CuteFTP like the plague. Joe can probably attest to that.

The answer is ncftp.

put -R *

True, I should've suggested that since I used ncftp to connect to my server from the clusters all the time. Sigh, I'm losing it.

incidently, why no cuteftp? adware/spyware? buggy? full of evil?

The real man writes his own ftp client

*not a real man

Full of Evil

iirc, high cpu utilization, slow, crappy interface, occasional crashes, evil reconnect of DOOM to piss off ftp servers (usually resulting in a very quick and persistent ban on your ip/domain), etc

The real men use telnet for ftp

quantus wrote:The real men use telnet for ftp

Gimme a sec to put up my packet sni... er, did I almost say that out loud

VLSmooth wrote:

quantus wrote:The real men use telnet for ftp

Gimme a sec to put up my packet sni... er, did I almost say that out loud

ftp IS in plain txt/binary

Peijen wrote:

VLSmooth wrote:

quantus wrote:The real men use telnet for ftp

Gimme a sec to put up my packet sni... er, did I almost say that out loud

ftp IS in plain txt/binary

Very true, but chances are getting an ftp login alone only lets you download. Getting a hold of a telnet account... now you're talking

Execution of arbitrary commands is a lot like inserting your penis into things. You want to be able to do it whenever and wherever you like, but you desperately want to prevent other people from doing so to you.

VLSmooth wrote:

Peijen wrote:

VLSmooth wrote: Gimme a sec to put up my packet sni... er, did I almost say that out loud

ftp IS in plain txt/binary

Very true, but chances are getting an ftp login alone only lets you download. Getting a hold of a telnet account... now you're talking

What I meant, peijen understood and you didn't get is that there is absolutely no difference between using a telnet client to connect to an ftp server and using some ftp client. I didn't mean to telnet and rcp or anything. I literally meant to telnet to the port of the machine with the ftp server and issue the raw commands from the term. You know all that stuff that gets dumped into the log window when you press a button? Those are commands you would have to type in the telnet window to do whatever it is you're doing. With that said, sniffing packets from the ftp client or the telnet session produce the exact same results: a login and password to the server only.

Interesting bitch-ass fact of the day:

ncftpput -R -u userid remotehost remotedir localdir

does not copy symlinks, only regular files and directories.

ncftpput -R -u userid remotehost remotedir localdir/*

however, adding the wildcard copies symlinks.

if you're a real man, you know the difference between PASV and PORT.

typically sym links are not copied because they can make the client loop infinitely since there's no way to check the inode of directory and know if it's been hit before. The only way that they typically implement it is to set a max depth of the directory structure.

Dwindlehop wrote:Execution of arbitrary commands is a lot like inserting your penis into things. You want to be able to do it whenever and wherever you like, but you desperately want to prevent other people from doing so to you.

This is because, of course, you want to do so in a beneficial way to all, whereas you suspect everyone else of wanting to hurt you.

Dwindlehop wrote:if you're a real man, you know the difference between PASV and PORT.

something that has to do with giving and recieving? you either you let others access you, or you access others. Actuall it's the other way around.

quantus wrote:What I meant, peijen understood and you didn't get is that there is absolutely no difference between using a telnet client to connect to an ftp server and using some ftp client. I didn't mean to telnet and rcp or anything. I literally meant to telnet to the port of the machine with the ftp server and issue the raw commands from the term. You know all that stuff that gets dumped into the log window when you press a button? Those are commands you would have to type in the telnet window to do whatever it is you're doing. With that said, sniffing packets from the ftp client or the telnet session produce the exact same results: a login and password to the server only.

Admittedly, this was a misinterpretation on my part. As for actually doing that, have fun, I'll take my client anyday

Dwindlehop wrote:if you're a real man, you know the difference between PASV and PORT.

iirc, PORT is sent from the client telling the server to connect to the client on a port specified by the client. PASV is also sent from the client, but asks the server to accept a data connection on a port selected by the server.

so in short:
PORT : server -> client
PASV : client -> server

I could be wrong, but if I'm right, I demand a cookie!

Wow, I've levelled up to Wanker Cadet, ph33r my slow technique!