webshell | This is a webshell open source project | Hacking library

i am making a fun little php webshell since i am pentesting for my exams and i have been stuck on a feature i want to add so it lets me see all of the files in the current directory. i have been stuck for quite a while here is the current code. EDIT:i want it to show all files in the webserver

We have a server deployed on amazon aws, the problem we are facing is that when ever there's a special character in the URL, it redirects to a 403 Forbidden error. It works fine on my local environment but not on live. See below

Does not work:

/checkout/cart/delete/id/243687/form_key/8182e1mPZIipGrXO/uenc/aHR0cHM6Ly93d3cuaG9iby5jb20ucGsvY2hlY2tvdXQvY2FydC8,

Works:

/checkout/cart/delete/id/243687/form_key/8182e1mPZIipGrXO/uenc/aHR0cHM6Ly93d3cuaG9iby5jb20ucGsvY2hlY2tvdXQvY2FydC8

Does not work:

/index.php/admin/catalog_product/new/attributes/OTI%253D/set/4/type/configurable/key/9f01c4b1a3f8c70002f3465b5899a54d

Works:

/index.php/admin/catalog_product/new/attributes/OTI253D/set/4/type/configurable/key/9f01c4b1a3f8c70002f3465b5899a54d

.htaccess for debugging

Given below is the htaccess code, but the thing is that this code works on my local.

I'm trying to use the JsonTypeAdapter in a modem to transmit some data from a remote source. The adapter is enabled through the modems startup script (JsonAdapter.enable()), and a TCP connection is established to the modem at port 1100. I follow the "Hello world" example in the Fjåge documentation and send the following JSON to the modem:

{"action":"send","message":{"clazz":"org.arl.unet.DatagramReq","data":{"data":{"clazz":"[B","data":"aGVsbG8gd29ybGQh"},"msgID":"8152310b-155d-4303-9621-c610e036b373","perf":"REQUEST","recipient":"phy","sender":"MyCustomInterface"}}}

I've set the logLevel to 'ALL' and can see that I get an incoming TCP connection in the log, but no data is being transmitted by the modem. I'm subscribing to the physical agent but am not getting any notifications in the WebShell (using UnetSocket works fine though).

I'm guessing that either the JsonAdapter isn't active on this TCP connection, the JSON string is faulty or not being sent properly by my application, or something else that I've missed.