Skip to content

Conversation

@Svieg
Copy link
Collaborator

@Svieg Svieg commented Apr 28, 2017

The refactor of the customization profiles have finally been tested and work. This removes the customization commands and moves that logic to a simpler json file in ~/.malboxes/customization (future work will involve creating examples for that). Tested on Ubuntu 16.04 and Windows 10 (with some bugs only found on Windows interestingly).

@Svieg Svieg requested a review from obilodeau April 28, 2017 21:26
@obilodeau
Copy link
Contributor

Code looks good however I would like to see the feature in action. Can you post an example customization? Ideally one that would trigger all code paths: registry, document, directory and package.

I would even consider it to be added as part of the smoke (build) automated testing.

@Svieg
Copy link
Collaborator Author

Svieg commented Jul 10, 2017

Agreed, I'll add at least one test customization profile!

if not os.path.exists(DIRS.user_config_dir):
os.makedirs(DIRS.user_config_dir)
os.makedirs(os.path.join(DIRS.user_config_dir, "customization"))
os.makedirs(os.path.join(DIRS.user_config_dir, "scripts", "user"))
Copy link
Contributor

Choose a reason for hiding this comment

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

We might want to use the cache directory here instead.

"{{ dir }}/scripts/windows/installtools.ps1"
"{{ dir }}/scripts/windows/installtools.ps1",
{% if customization_profile %}"{{ config_dir }}/scripts/user/{{ customization_profile }}.ps1",{% endif %}
"{{ dir }}/scripts/windows/malware_analysis.ps1"
Copy link
Contributor

Choose a reason for hiding this comment

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

This change will need to be repeated in the new provision_powershell_win7.json file

@obilodeau
Copy link
Contributor

We need the documentation to be updated to reflect that we support that also.

@obilodeau
Copy link
Contributor

As discussed, we think it should be clearer that this feature is what we will refer to from now on as profiles.

What we previously called a profile will now be referred to as a template.

@obilodeau
Copy link
Contributor

I think we are near completion here.

If the variable is unset profiles are not used by default.

If a profile name refers to no file on the filesystem, then a default
one will be created based on our example config.
@obilodeau obilodeau merged commit b5b757f into master Jul 25, 2017
@obilodeau obilodeau deleted the profiles branch September 18, 2018 19:08
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.

3 participants