Page 3 of 3 FirstFirst 123
Results 21 to 24 of 24

Thread: zypper SOCKS 5 proxy

  1. #21
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,153
    Blog Entries
    2

    Default Re: zypper SOCKS 5 proxy

    Quote Originally Posted by JLemur View Post

    Here are some other threads I found regarding zypper and proxychains, neither of which had a resolution:
    https://forums.opensuse.org/showthre...entation-fault
    https://www.linuxquestions.org/quest...xy-4175430212/
    Neither of your references are likely helfpful to anybody...
    A question is asked but without any detail.
    In the openSUSE Forums post, there was no answer.
    In the linuxquestions post, the @OP appeared to change from setting up a SOCKS connection to setting up an Web Proxy (http) instead which is what I've suggested.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  2. #22

    Default Re: zypper SOCKS 5 proxy

    Quote Originally Posted by tsu2 View Post
    OK,
    I'll try to find some time (can't guarantee) to set up a proxy and test using proxychains and zypper...
    I very much appreciate this as I can't seem to get it to work.

    Backing up though,
    In the beginning I asked whether you have any kind of control over your proxy server...
    It's common for a proxy server on the edge of your network to support http/https proxying(ie Web Proxy server which is different functionality than a SOCKS5 Proxy Server)...
    If your web browsers can browse the Internet, then you likely have that configured. and should be the simplest way to connect... If your web proxy doesn't require credentials or credentials are automatically passed (eg by LDAP or AD), then it should be the simplest solution... the https connection should work and there should not be a need to use SOCKS.
    There is no Web proxy server in the network. The servers which are in the same zone as serverB (openSUSE) do not have any access to the internet. They are all operating as a self-contained network with some entry points such as ssh from serverA. The only way to access the internet is to tunnel back through ssh, and for this only serverB will be used. serverB will be a "utility server" supplying different services to the other servers in its zone, e.g. a docker repository/simple DNS server/ldap/etc. serverB can reach all the other servers in its zone, but none of them have internet access.

    BTW -
    I'll ask one last time,
    Don't know if you're overlooking or deliberately avoiding an answer...
    What is your proxy server application?
    I've intended to answer this question by pointing out that I'm using ssh as a SOCKS5 proxy server. From the ssh man page:

    Code:
         -D [bind_address:]port
                 Specifies a local “dynamic” application-level port forwarding.  This works by allocating a socket to listen to
                 port on the local side, optionally bound to the specified bind_address.  Whenever a connection is made to this
                 port, the connection is forwarded over the secure channel, and the application protocol is then used to deter‐
                 mine where to connect to from the remote machine.  Currently the SOCKS4 and SOCKS5 protocols are supported,
                 and ssh will act as a SOCKS server.  Only root can forward privileged ports.  Dynamic port forwardings can
                 also be specified in the configuration file.

  3. #23
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,153
    Blog Entries
    2

    Default Re: zypper SOCKS 5 proxy

    OK, I see about using SSH as your proxy server...

    Then since it appears that you do have control over your "proxy server" that you should consider setting it up as a Web Proxy in addition to or instead of as a SOCKS proxy. Although I haven't read the documentation fully, I assume like any other proxy server you'll have a full array of options to configure your client-side security however you wish... ranging generally from the simple IP address include/exclude to machine and User based credlentials, and the credential types can be varied.

    In other words, if ServerA can be configured as a web proxy server even for just your one (or group) of openSUSE machines, then zypper on your openSUSE should "just work" and not require anything like proxychains... unless you do something like configure listening only on a strange port but in those cases I'd expect the YaST proxy client to do what is necessary.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #24
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,153
    Blog Entries
    2

    Default Re: zypper SOCKS 5 proxy

    And here's another thought...

    Although I still would recommend setting up your proxy as a Web Proxy and not as a SOCKS proxy server as the recommended, simplest way to set up largely because it should support a direct connection from your openSUSE to the proxy server without any other apps and "just work,"

    Let's say that some company rule blocks any kind of connection except an SSH connection (although up to this point you've been asking about a SOCKS configuration).

    Got me to thinking about, and verified there are an abundance of articles on setting up an "HTTP over SSH" tunnel...
    A quick skim of a few articles suggests it's easy to set up...
    - Configure a fairly standard ssh proxy server on one end, and a ssh client on the other end, but listening on a specified port (likely port 80 and 443).
    - Point your application to the SSH client likely running on your local machine (localhost and port number) which can be done using the YaST proxy module.
    -All traffic between your SSH client and SSH proxy server of course travels as SSH.
    - Done!

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •