powered by Jive Software

SOCKS5 proxy access


Is there a way with Openfire to control access to the bytestream proxy? I’'m curious to know whether I could be running my proxy wide open or else restricted in some regard. Ad hoc tests indicate that the proxy is not wide-open (e.g. one of the users in the file transfer has to be a local user). Is that the correct behaviour?

All-in-all, I hoping that maybe there’'s something more then the “Enable/Disable” control from the web interface.


Currently, as you have discovered, the only control over this is that one of the users has to be connected to the server. This requirement can be disabled.