View Issue Details

IDProjectCategoryView StatusLast Update
0006626Kali LinuxKali Package Bugpublic2021-03-09 11:11
ReporterOS-74160 Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2020.2 
Summary0006626: syntax warnings during post-install setup of powershell-empire (possible upstream issue)
Description

Installing powershell-empire from a clean slate via apt results in syntax warnings during the setup phase:
Setting up powershell-empire (3.3.1-0kali1) ...

[] Certificate written to ../data/empire-chain.pem
[
] Private key written to ../data/empire-priv.key

/usr/share/powershell-empire/data/agent/agent.py:357: SyntaxWarning: "is not" with a literal. Did you mean "!="?
if cmdargs is not None and cmdargs is not '' and cmdargs is not '/': # strip trailing slash for uniformity
/usr/share/powershell-empire/data/agent/agent.py:357: SyntaxWarning: "is not" with a literal. Did you mean "!="?
if cmdargs is not None and cmdargs is not '' and cmdargs is not '/': # strip trailing slash for uniformity
/usr/share/powershell-empire/data/agent/agent.py:359: SyntaxWarning: "is not" with a literal. Did you mean "!="?
if path[0] is not '/': # always scan relative to root for uniformity
Processing triggers for kali-menu (2020.3.2) ...

Steps To Reproduce
  1. Download a brand new Kali 2020.2a VMware image from the OffSec website
  2. sudo apt -y install powershell-empire
  3. Observe the installation complete and syntax warnings occur during "Setting up powershell-empire" phase
Additional Information

Presumably, this could be fixed by modifying line 357 of /usr/share/powershell-empire/data/agent/agent.py as suggested in the warning, but I have not tested this.

Activities

OS-74160

OS-74160

2020-08-06 10:17

reporter   ~0013211

Under additional information, I should have said,

"Presumably, this could be fixed by modifying lines 357 and 359 of /usr/share/powershell-empire/data/agent/agent.py as suggested in the warning, but I have not tested this."

sbrun

sbrun

2021-03-09 11:11

manager   ~0014296

it is now fixed in the gitlab repository of powershell-empire

Issue History

Date Modified Username Field Change
2020-08-06 10:14 OS-74160 New Issue
2020-08-06 10:17 OS-74160 Note Added: 0013211
2021-03-09 11:11 sbrun Assigned To => sbrun
2021-03-09 11:11 sbrun Status new => resolved
2021-03-09 11:11 sbrun Resolution open => fixed
2021-03-09 11:11 sbrun Note Added: 0014296