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

No pshtt.zip file in 'develop' branch #29

Closed
refayathaque opened this issue Mar 6, 2019 · 9 comments · Fixed by #42
Closed

No pshtt.zip file in 'develop' branch #29

refayathaque opened this issue Mar 6, 2019 · 9 comments · Fixed by #42
Assignees
Labels
bug This issue or pull request addresses broken functionality

Comments

@refayathaque
Copy link

Hi guys,

Upon cloning the repo and running all commands in the readme I do not get the pshtt.zip file, however, once I switch into the master branch I do. Is there something different we need to do to build the pshtt.zip file using Docker in the develop branch?

Thank you,

@jsf9k jsf9k self-assigned this Mar 8, 2019
@jsf9k
Copy link
Member

jsf9k commented Mar 8, 2019

@refayathaque, thanks for the issue. Is this the error you're seeing?

/venv/bin/activate: line 31: $1: unbound variable

I ran into that myself today, and I created #32 to fix it. Please let me know if this is the same issue you are seeing.

@jsf9k jsf9k added the bug This issue or pull request addresses broken functionality label Mar 8, 2019
@jsf9k
Copy link
Member

jsf9k commented Mar 11, 2019

@refayathaque, #32 is now merged. Give that a try and let us know if that fixes the issue you were seeing (or not).

@jsf9k
Copy link
Member

jsf9k commented Mar 20, 2019

I am going to close this issue since I believe it is fixed. @refayathaque, please reopen it if I haven't fixed the problem you were seeing.

@jsf9k jsf9k closed this as completed Mar 20, 2019
@refayathaque
Copy link
Author

Hi @jsf9k

Sorry I'm getting to this so late. Ummm I don't think we are talking about the same thing. So I am using this repo to build myself Lambda deployment packages for pshtt and trustymail. I'm not using this with domain-scan. Based on your instructions in the README, 'Building the environment zip files for all scanners and deploying them to AWS Lambda using domain-scan:', what I am having issues within the develop branch is step # 3, after running docker-compose up I am not seeing the pshtt.zip, trustymail.zip, and sslyze.zip files. However, once I run docker-compose up from the master branch I do see the .zip files.

It's not a massive issue but just wanted to bring it to your attention.

Thank you!

@jsf9k
Copy link
Member

jsf9k commented Jun 27, 2019

@refayathaque, the master branch is woefully out of date. You really want to be building from the develop branch. Can you share the output of docker-compose build && docker-compose up when you run it from the develop branch?

@refayathaque
Copy link
Author

Hi Shane @jsf9k

Attached are some screenshots that should explain what is going on. Appreciate the help!

Screen Shot 2019-07-01 at 11 31 08 AM
Screen Shot 2019-07-01 at 11 24 18 AM
Screen Shot 2019-07-01 at 11 22 29 AM
Screen Shot 2019-07-01 at 11 21 59 AM

@jsf9k
Copy link
Member

jsf9k commented Jul 5, 2019

You should definitely be using the develop branch. Thanks for the screenshots; I think I see the problem you're having. I'll create a pull request now.

@jsf9k jsf9k reopened this Jul 5, 2019
jsf9k added a commit that referenced this issue Jul 5, 2019
It is causing the activate script to error out for some folks.  This
resolves #29.
@jsf9k
Copy link
Member

jsf9k commented Jul 5, 2019

@refayathaque, can you check out branch bugfix/fix_unbound_var_error and let me know if it resolves your issue? Thanks!

@jsf9k jsf9k closed this as completed in #42 Jul 8, 2019
@refayathaque
Copy link
Author

@jsf9k thank you so much! docker-compose build and up from develop branch yielding zip files! Also when you get a chance can you please have a look at trustymail, I still keep getting that darn module 'DNS' has no attribute 'Type' when I try to run it in Lambda (I've tried Python 2.7, 3.6 and also 3.7). cisagov/trustymail#41 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request addresses broken functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants