Site Tools


dcc_get

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dcc_get [2006/09/01 18:32] (current)
Line 1: Line 1:
 +# $EPIC: dcc_get.txt,​v 1.4 2006/08/31 11:57:06 sthalik Exp $
 +======Synopsis:​======
 +[[dcc]] get [=]<​nick>​ <​file>​ [file2] [file3] ... \\
 +[[dcc]] get [=]<​nick>​ <​file>​ [file2] [file3] ... /directory \\
 +[[dcc]] get [=]<​nick>​ <​file>​ <​not-offered-file>​ \\
 +[[dcc]] get [=]<​nick>​
 +
 +======Description:​======
 +[[DCC]] __GET__ opens a file transfer connection and downloads a file
 +that someone else has offered you with the [[DCC SEND]] command.
 +
 +If the file offer was received over a [[DCC CHAT]] connection that you
 +have open with the person, then you must use their [[DCC CHAT]] nickname
 +(eg, with a = before their nickname) as the nickname.
 +
 +If you do not specify the filename to get, the first (oldest) pending
 +offer to you from that nickname will be opened. ​ If you wish to open
 +all offers to you from that person, you can use the star ('​*'​) argument.
 +Note that this is not a wildcard; you cannot specify a wildcard pattern
 +as the filename argument. ​ It must either be the name of a file, the 
 +star character, or nothing at all.
 +
 +If you specify two file names: one offered and one not, file will be
 +renamed to the name that's not offered and accepted for transfer.
 +
 +If you specify one or more files and a directory as the last parameter,
 +file(s) will be downloaded to this directory.
 +
 +If you specify a nick but no files, all the files offered by given nick
 +will be accepted for transfer.
 +
 +You must be able to establish an outbound internet connection from your host
 +and the other person must be able to accept an inbound internet connection to
 +their host.  If either of these requirements are not met, (ie, there is a
 +firewall in the way) the connection will fail.  This is not a bug in EPIC or
 +the [[DCC]] specification;​ this is just how the internet works.
 +
 +======Security Considerations:​======
 +The content of files sent by other users may be potentially harmful. You should
 +know what a file is and trust the sender before accepting a [[DCC]] transfer.
 +Malicious arguments may also be part of the DCC handshake, potentially creating
 +a denial of service attack if the user accepts such a malicious DCC handshake.
 +Accepting a [[DCC]] transfer also provides the sender with the recipient'​s IP
 +address. On networks which hide this information,​ this could potentially be
 +used as part of a social engineering tactic in order to obtain a user's IP
 +address. The client will convert a leading dot (.) in a filename to an
 +underscore (_) to prevent other users from sending dotfiles.
 +
 +======Examples:​======
 +To accept a SEND from bob:
 +      /dcc get bob
 +
 +To accept all files offered to you by DCCbot:
 +      /dcc get DCCbot *
  
dcc_get.txt ยท Last modified: 2006/09/01 18:32 (external edit)