Skip to content

Commit

Permalink
update nuclei to v3, updated go to v1.21.4, closes #1033
Browse files Browse the repository at this point in the history
  • Loading branch information
@yogeshojha
yogeshojha committed Nov 15, 2023
1 parent c145bec commit c2f891a
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions web/Dockerfile
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,9 @@ RUN apt install -y --no-install-recommends \
RUN add-apt-repository ppa:mozillateam/ppa

# Download and install go 1.20
RUN wget https://golang.org/dl/go1.20.linux-amd64.tar.gz
RUN tar -xvf go1.20.linux-amd64.tar.gz
RUN rm go1.20.linux-amd64.tar.gz
RUN wget https://golang.org/dl/go1.21.4.linux-amd64.tar.gz
RUN tar -xvf go1.21.4.linux-amd64.tar.gz
RUN rm go1.21.4.linux-amd64.tar.gz
RUN mv go /usr/local

# Download geckodriver
Expand All @@ -74,7 +74,7 @@ RUN go install -v github.com/tomnomnom/unfurl@latest
RUN go install -v github.com/tomnomnom/waybackurls@latest
RUN go install -v github.com/projectdiscovery/httpx/cmd/httpx@latest
RUN go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest
RUN go install -v github.com/projectdiscovery/nuclei/v2/cmd/nuclei@latest
RUN go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest
RUN go install -v github.com/projectdiscovery/naabu/v2/cmd/naabu@latest
RUN go install -v github.com/hakluke/hakrawler@latest
RUN go install -v github.com/lc/gau/v2/cmd/gau@latest
Expand Down

5 comments on commit c2f891a

@AnonymousWP
Copy link
Contributor

Choose a reason for hiding this comment

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

Why in the 2.0.1 branch? 2.0.1 is already released.

@yogeshojha
Copy link
Owner Author

Choose a reason for hiding this comment

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

my bad, should have been 2.0.2

@AnonymousWP
Copy link
Contributor

Choose a reason for hiding this comment

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

my bad, should have been 2.0.2

You're also aware we're not merging to the 2.0.2 branch yet right? Maybe let's do that with 2.1.0 upwards? So merge all changes to the 2.1.0 branch, then when 2.1.0 is all set, merge 2.1.0 to master and create a release.

@yogeshojha
Copy link
Owner Author

Choose a reason for hiding this comment

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

No, this is related to

#1033

v2 had installation errors, and v2 requires go 1.21 upwards.

@AnonymousWP
Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah okay, so feel free to open a PR from a branch so Psyray and I can review & approve. Critical for 2.0.2.

Please sign in to comment.