Powershell Error from client
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 765
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am getting an error from the client when it successfully connects back to my listener ive pasted some output below;
##Listener Sucessfully Running
Octopus >>listeners
Name IP Port Host Interval Path SSL
--------- ------- ------ -------------- ---------- -------- -----
listener1 0.0.0.0 80 192.168.80.129 5 page.php False
##Session Started on target
Session IP Hostname Process Name / PID / Arch Username Domain Last ping OS
--------- ------------ ----------------- --------------------------- ---------- --------- ------------------------ --------------------------------
2 192.168.80.1 TestHost-PWYVI powershell (21060) - x64 test* WORKGROUP Thu Nov 12 11:30:11 2020 Microsoft Windows 10 Pro(64-bit)
##Error Received each time host checks in
Octopus >>
Command execution result is :
Invoke-Expression : Cannot bind argument to parameter 'Command' because it is an empty string.
At line:144 char:33
+ $ec = Invoke-Expression ($fc) | Out-String;
+ ~~~~~
+ CategoryInfo : InvalidData: (:) [Invoke-Expression], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.Invo
keExpressionCommand
I have tried several different generation methods each with the same results, I have turned AV off but still the same error.
Please could you assist?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the PowerShell client check-in against the listener configuration shown in the report, then inspect the generated client around line 144 where Invoke-Expression receives $fc. The issue is resolved when repeated check-ins no longer produce the empty-command error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100