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
Not sure what's going on. I suspect it's a linux vs windows rtr scripts issue. Confirmed by unaliasing the commands using auditd & script block logging. ( haha )
/ # cat /home/user/.bash_history -h
Usage: cat [-h] [-b] file
Read a file from disk and display as ASCII or hex.
positional arguments:
file File to read the contents of
optional arguments:
-h, --help show this help message and exit
-b, --ShowHex Show the results in hexadecimal byte format instead of ASCII
/ # cat -b /home/user/.bash_history
Executing command: cat /home/user/.bash_history -ShowHex
hostname:
At least one error was detected. Check the log file for full details.
List of errors detected:
Not sure how the translation to actual parameters from RTR options is made under the hood.
PARAMETER WD
Current working directory
PARAMETER Param1
File to concatenate
PARAMETER Param2
Number of bytes to read (max=32768)
PARAMETER Param3
Offset (in byte value) to start reading from
PARAMETER Param4
Show the results in hexadecimal format
The bash script doesn't seem to have the same options, and the associated code doesn't seem to implement any of these (???)
# PARAMETER WD# Current working directory# PARAMETER Param1# File to concatenate# PARAMETER Param2# Number the output lines starting from 1# PARAMETER Param3# Display non-printing characters, and display tab characters as `^I'.
Not sure if the problem lies in falcon-toolkit offering options that don't exist on linux, or in RTR scripts that don't support doing advanced hacking techniques known as "a hex dump" :D
Cheers
The text was updated successfully, but these errors were encountered:
Thanks for raising! I believe this is due to a difference in the RTR commands offered on Windows and Linux. Given that you can connect to systems across multiple operating systems at the same time, we do not filter or modify the available commands or parameters by OS.
Besides, restricting this would require dynamically deciding which parameters to include in each command's argparser at runtime which would be quite complex for relatively little gain. I believe this can be solved with some better documentation, but I'd be open to alternatives here.
Not sure what's going on. I suspect it's a linux vs windows rtr scripts issue. Confirmed by unaliasing the commands using auditd & script block logging. ( haha )
On windows it works
Not sure how the translation to actual parameters from RTR options is made under the hood.
The bash script doesn't seem to have the same options, and the associated code doesn't seem to implement any of these (???)
Not sure if the problem lies in falcon-toolkit offering options that don't exist on linux, or in RTR scripts that don't support doing advanced hacking techniques known as "a hex dump" :D
Cheers
The text was updated successfully, but these errors were encountered: