# $EPIC: get,v 1.6 2002/09/19 23:52:15 dinodrac Exp $
Synopsis:
   dcc get [=]<nick> [<file>]

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.

   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 *



See Also:
   dcc(1) rename, resume, send; set(4) dcc_store_path