View Issue Details

IDProjectCategoryView StatusLast Update
0006449Kali LinuxKali Package Bugpublic2020-06-16 06:21
Reportercohst Assigned Tosbrun  
Status resolvedResolutionfixed 
Product Version2020.2 
Summary0006449: After Upgrade powershell-empire can't be loaded any more

After I did apt-get update && apt-get dist-upgrade, Empire doesn't start anymore and shows an error message.

Steps To Reproduce

Update to latest version and start powershell-empire

Attached Files
pwemp.JPG (122,647 bytes)   
pwemp.JPG (122,647 bytes)   
pwemp2.JPG (101,071 bytes)   
pwemp2.JPG (101,071 bytes)   




2020-06-13 08:34

manager   ~0012915

Last edited: 2020-06-13 08:38

Upstream has updated the db schema. You have to run "powershell-empire --reset"

I have added an information about this in the package: see /usr/share/doc/powershell-empire/NEWS.Debian.gz



2020-06-13 11:20

reporter   ~0012916

I have tested this now, but unfortunately it doesn't work (at least for me). See Screenshot.



2020-06-15 07:25

manager   ~0012918

Don't run the reset db with sudo if you usually run powershell-empire without sudo:
the database is located in ~/.local/powershell-empire/

If you run the reset with sudo, it will reset / setup the database in /root/.local/powershell-empire.

And after, if you run powershell-empire without sudo, it will use the database in /home/current-user/.local/powershell-empire



2020-06-15 19:07

reporter   ~0012925

OK, that works! I have just tested it and it starts normal, after creating the database scheme new. Thx so far.

Issue History

Date Modified Username Field Change
2020-06-12 19:46 cohst New Issue
2020-06-12 19:46 cohst File Added: pwemp.JPG
2020-06-13 08:34 sbrun Assigned To => sbrun
2020-06-13 08:34 sbrun Status new => confirmed
2020-06-13 08:34 sbrun Note Added: 0012915
2020-06-13 08:38 sbrun Note Edited: 0012915
2020-06-13 11:20 cohst Note Added: 0012916
2020-06-13 11:21 cohst File Added: pwemp2.JPG
2020-06-15 07:25 sbrun Note Added: 0012918
2020-06-15 19:07 cohst Note Added: 0012925
2020-06-16 06:21 sbrun Status confirmed => resolved
2020-06-16 06:21 sbrun Resolution open => fixed