- You should see a blue [Owned] next to the process that belongs to your gateway in remote systems "Running Software". This helps identify your own processes.
- Bounce connection has been improved, once you bounce every action you make on the remote server is logged with the last bounce IP not the gateway IP. This does pose some identification issues when accessing the "Running Software" of the remote host to complete a task since the task will be marked with the last IP you bounced, but the update that tags [Owned] to your processes will help here.
- Anti-virus will not detect hidden active virii, but it will report that there is something hidden it can not see, and you should run a better File UnHider on the gateway to be able to AV the file. This makes hiding of active virii very important to protect them against AV.
- When an upload is finished and task is completed, the bandwidth will adjust on your gateway properly to run the other download / uploads.
- Anti-virus on Public and Secret servers can be run with more then 100% CPU / memory. This is because there are disinfect missions that require the AV to run on the server.
- added a little log link next to the process type, when clicking this log link it will open up the connection server lol of the admin that made the process.
- bounce connection will make a log on the previous and next target, something like "Proxy connection from [IP] to [IP] established."
- the origin of the proxy connection will look like this in the server logs: "Origin proxy connection to [IP] established." The server with this log is the first link of the bounce.
- log time when doing a bounce is preserved to keep the consistency of the bounce, e.g. if you connect at 00:00 to the first node and then at 00:10 to the next, the logs will be entered at 00:00 time. This should make bounce connections easier to track down.
- increased the public servers capacity and power so they can hold more virii
