Skip to content

Can't Paste Multiple Commands #2283

Description

@NoPurposeInLife

Is your feature request related to a problem? Please describe.

Previously, I was able to paste multiple commands into the Sliver console, and they would be executed sequentially without any issues. This was very convenient when performing repetitive tasks such as uploading multiple files.

After updating to a newer version, this no longer works. Pasting multiple commands now results in the following error:

Error: accepts between 1 and 2 arg(s), received 11

For example, the following previously worked when pasted together:

upload "/root/Desktop/Games/Hacking_Tools/Post_Exploitation/Windows/System Passwords/mimikatz-2.1.1/x64/mimilib.dll" "C:/Users/Public/Documents/mimilib.dll"
upload "/root/Desktop/Games/Hacking_Tools/Post_Exploitation/Windows/System Passwords/mimikatz-2.1.1/x64/mimikatz-2.1.1.exe" "C:/Users/Public/Documents/mimikatz-2.1.1.exe"
upload "/root/Desktop/Games/Hacking_Tools/Post_Exploitation/Windows/System Passwords/mimikatz_trunk/x64/mimikatz.exe" "C:/Users/Public/Documents/mimikatz.exe"
upload "/root/Desktop/Games/Hacking_Tools/Post_Exploitation/Windows/System Passwords/mimikatz-2.1.1/x64/mimidrv.sys" "C:/Users/Public/Documents/mimidrv.sys"

Instead of executing each command individually, the console appears to interpret the entire pasted block as a single command, resulting in the argument parsing error.

Describe the solution you'd like

It would be great if the console could once again support pasting multiple newline-separated commands and execute them sequentially, as it did previously.

If this behavior was intentionally changed, an alternative would be to add an option or configuration to enable multi-command paste support.

Describe alternatives you've considered

The current workaround is to paste and execute each command individually, or create and execute a script. However, this is significantly slower and less convenient, especially during post-exploitation workflows where multiple upload commands are commonly used.

Additional context

The issue appears to have been introduced after updating, as the exact same workflow worked correctly in previous versions. If this is an unintended regression, restoring the previous behavior would greatly improve usability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions