Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

drakrun: improve draksetup log output #450

Merged
merged 10 commits into from
Mar 1, 2021
Merged

Conversation

manorit2001
Copy link
Contributor

This PR contains minor improvements which can help users during the installation process

Signed-off-by: manorit chawdhry <manorit2001@gmail.com>
@manorit2001
Copy link
Contributor Author

@chivay which linter should we use for auto-formatting the files?

@manorit2001
Copy link
Contributor Author

Also, is there any specific reason for choosing 4096 as the block size during the calculation of the hash?

- the download speed comes to be in kbs which can be increased by
  increasing the chunk size
drakrun/drakrun/draksetup.py Outdated Show resolved Hide resolved
@icedevml
Copy link
Contributor

Also, is there any specific reason for choosing 4096 as the block size during the calculation of the hash?

I think it was pretty arbitrary, can be changed to some more feasible value if it really speeds up the calculation.

@icedevml
Copy link
Contributor

which linter should we use for auto-formatting the files?

You can check that in the CI logs:
https://drone.icedev.pl/CERT-Polska/drakvuf-sandbox/1643/2/2

cd drakrun && flake8 --ignore E402,F401,E501

@icedevml
Copy link
Contributor

This PR looks OK to me in general 👍 . Please rename the title to something more feasible, e.g. drakrun: improve draksetup log output, fix linter errors and I think it can be merged then.

manorit2001 and others added 2 commits February 28, 2021 20:27
Co-authored-by: Michał Leszczyński <ml@icedev.pl>
- secrets library is cryptographically more better for randomness
@manorit2001
Copy link
Contributor Author

I think it was pretty arbitrary, can be changed to some more feasible value if it really speeds up the calculation.

I haven't really benchmarked anything but just looking at the memory footprint of draksetup, It looked like we can utilize ram more so just tried to increase the value

@manorit2001 manorit2001 changed the title Minor Improvements drakrun: improve draksetup log output Feb 28, 2021
@manorit2001 manorit2001 marked this pull request as ready for review February 28, 2021 15:40
Copy link
Contributor

@icedevml icedevml left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

drakrun/drakrun/drakpdb.py Outdated Show resolved Hide resolved
drakrun/drakrun/draksetup.py Outdated Show resolved Hide resolved
drakrun/drakrun/draksetup.py Outdated Show resolved Hide resolved
drakrun/drakrun/draksetup.py Show resolved Hide resolved
@manorit2001 manorit2001 requested a review from chivay March 1, 2021 16:53
drakrun/drakrun/draksetup.py Outdated Show resolved Hide resolved
@chivay chivay merged commit 8e92a04 into CERT-Polska:master Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants