You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
💭
$ ps auxf # hey, what's happening?
George Murdocca
gmurdocca
💭
$ ps auxf # hey, what's happening?
Linux DevOps/Software engineer, trainer and founder at linuxdojo.com
Development and Build Environment Setup for VESC Tool
Warning
This howto is unfortunately outdated and no longer works. Please see comments below.
This guide lists the steps necessary to produce a development and build environment for the VESC Tool application, including building the Android APK package.
Circumventing Deep Packet Inspection with Socat and rot13
I have a Linux virtual machine inside a customer's private network. For security, this VM is reachable only via VPN + Citrix + Windows + a Windows SSH client (eg PuTTY). I am tasked to ensure this Citrix design is secure, and users can not access their Linux VM's or other resources on the internal private network in any way outside of using Citrix.
The VM can access the internet. This task should be easy. The VM's internet gateway allows it to connect anywhere on the internet to TCP ports 80, 443, and 8090 only. Connecting to an internet bastion box on one of these ports works and I can send and receive clear text data using netcat. I plan to use good old SSH, listening on tcp/8090 on the bastion, with a reverse port forward configured to expose sshd on the VM to the public, to show their Citrix gateway can be circumvented.
Rejected by Deep Packet Inspection
I hit an immediate snag. The moment I try to establish an SSH or SSL connection over o