Your best friend for file transfer.

Fetch application logoFetch

socks5 and prosy authentication (6 posts)

  • Started 7 years ago by jimbo237
  • Latest reply 7 years ago from Scott McGuire
  • jimbo237 Member

    I have some users running MAC version 10.3.9 that needed FTP access through a BlueCoat proxy. I had them purchase Fetch version 5.0.5. Whenever I set the proxy option to use socks5 the username and password field get greyed out and do not allow me to enter a proxy ID and password. How can I use socks5 with a username and password?

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    I'm sorry, but Fetch does not support SOCK5 authentication at this time.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • jimbo237 Member

    Any idea if/when socks5 proxy authentication will be included or the proxy format of USER User@Host FireID as the Fetch included formats for User/Host/FireID are not supported by our Proxies?

    Thanks in advance.

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    We do not have a set date for SOCKS 5 authentication, but it is on our to-do list.

    We believe that Fetch does support the "USER User@Host FireID" proxy format (listed in the Proxy type menu as "USER remoteID@remoteHost fireID". If you tried it and it's not working for you, we'd like to hear more about how it it doesn't work so we can investigate. What happens when you choose it, and could you post a transcript of the failure (choose Window > Fetch Transcript and post the contents of that window here)?

    Or did you mean there is another FireID proxy format you're looking for? If so, please describe it to us so we can look into adding it.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 04-20-2006).]

    Posted 7 years ago #

  • jimbo237 Member

    The "USER User@Host FireID" proxy format (listed in the Proxy type menu as "USER remoteID@remoteHost fireID" did actually work, the only extra thing I needed to do was to suppy a bogus password for the "anonymous" user (jim@). Thanks for all of your help.

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    You're welcome, and thanks for the followup information. We're glad to hear you got it working.

    Please let us know if you have any more questions.

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.