Minor findings in installation, startup and usage of EMBArk about embark

[BenediktMKuehne]

Hi torabi,

the uploader and the reporter problem are there for anti code-injection stuff.
They will eventually be back to working as expected.

The progress-bar overhaul is on the TODO-list. It has some design flaws at the moment.

the warnings etc in #53

[torabi12]

I checked the same on Kali 2022.3.

During the EMBArk installation there were these warnings:

I use a brand new workstation with 11th gen i7 CPU with latest BIOS but I got this more times:

and the final one:

Usage of EMBArk:
Same fakepath as on Ubuntu and on Kali:

The progress bar also stopped again but the scan has been finished for sure:

and the final report is incomplete:

OS: Kali 2022.3
VMware Workstation Pro 16

[BenediktMKuehne]

pipenv warnings are related to this pypa/pipenv#5208

[m-1-k-3]

pipenv warnings are related to this pypa/pipenv#5208

Thank you for the resource. We have such warnings in multiple areas in EMBA.

[torabi12]

Hello Benedikt,

I checked today the upload and reporting in EMBArk and I have these info:

I added these parameters:

and I got this back:

The final report would be important I think because the user would store only the html pages of the scans.
Could you check it on your side please? Thank you.

[m-1-k-3]

@torabi12 please open a new ticket for better tracking

Thank you