arglanir / remote-connection-anywhere

Project in order to create connections to a protected zone, through async means

Remote-connection-anywhere

Short description

I created this project in order to create connections to an otherwise protected zone, through async means (shared folder, e-mail)

It shows also some tests when working with sockets.

Architecture

Communication client ⇆ Communication layer ⇆ Action server

Communication layers

Client ⇆ Session ⇆ Physical mean ⇆ Session ⇆ Server

• ✅ Bases classes (CommunicationSession CommunicationClient CommunicationServer))
• ✅ Test communication through queue (QueueCommunicationSession))
• ✅ Exchange of files through folder (like NFS, or shared folder) (FolderCommunicationSession FolderCommClient FolderCommServer))
• ✅ FTP (FtpCommServer FtpCommunicationSession FtpCommClient)
• ✅ Imap (e-mail server) (Imap4CommServer ImapCommSession Imap4CommClient)
  • 💡 Imap with notifications/shared connections (otherwise multiple searches may be too big for the server)
• 💡 Socket (not really useful)

Action clients / servers

• ✅ For test: (EchoActionServer StoreAllActionServer)
• ✅ Console / ✅Shell (Bash or other program) communicating with stdin/stdout/stderr (GenericPipeActionServer PipeActionServer PipeLineClient)
• ✅ Socket / Connection to other socket (ssh, rdesktop, vnc)
• ✅ Socket / Connection to local socket
• ✅ Http proxy (TcpSocketActionServer runLocalServerForRemoteClient) and (serverOwnProxyOnFolder.py)
• ✅ SOCKS proxy v4 and v4a! (Socks4Backend SocksFrontEnd)

Transverse

• ✅ : Method to clean shared space

💡 : ideas

🚧 : in construction

✅ : complete

Credential managers

See src/remoteconanywhere/cred.py

• ✅ .netrc file
• ✅ local file

What to do next?

• 💡 : commands to all/one servers:
  • redistribute capabilities (if cleaned by a client)
  • stop
  • display statistics (opened sessions, all sessions since start, etc)

How to run it

###### on the server side:

from remoteconanywhere.communication import *
from remoteconanywhere.pipe import *

# choose and configure one server
server = FolderCommServer('/path/to/folder')
# register action servers
server.registerCapability(GenericPipeActionServer())
server.registerCapability(PipeActionServer(sys.executable, '-i', '-u'))
server.registerCapability(PipeActionServer('/bin/bash', '-i'))
# start the server
server.serveForever()



###### on the client side:

# select the client to use
client = FolderCommClient('/path/to/folder')
# check server/capabilities
client.listServers()
client.capabilities('serverid')
# open a session, give it to the capability client
session = client.openSession('serverid', 'pipe')
PipeLineClient(session).start()

How to run it (old)

🚧 In construction, old API, kept here for the parameters, when a new bash api will be written

python3 test_socket.py asyncio 8910 www.google.com 443 &
wget --no-check-certificate https://127.0.0.1:8910

python3 remoteconanywhere.py --help

python3 remoteconanywhere.py imaptest --host imap.gmail.com:ssl

remote-connection-anywhere's Issues

Imap server closes connection after some hours even when searching for message every 5 seconds.

This may be problematic when a durable connection want to persist during more than a few hours.

Encapsulate every call to the server to handle abort messages, in order to start a new connection ?
What about stored uids ? Are they still valid ?

Implement SOCKS 5 protocol

Maven uses only socks 5 protocol, so in order to use this proxy, this protocol must be implemented.

Collisions when opening two sessions at the same time

This problem may appear if a client is used in two different threads to open a session.

Change of protocol: The message numbers sent/received should increase.

Compatibility with pytest

test/configurationoftests.py must have everything. Or maybe if import error, use a mock in the tests.

To run pytest:
PYTHONPATH=src:test pytest