Skip to content

Commit

Permalink
Merge pull request #434 from owasp-noir/release-0-18
Browse files Browse the repository at this point in the history
Release-0-18
  • Loading branch information
hahwul authored Oct 31, 2024
2 parents e6c1010 + 7915248 commit c2c4e15
Show file tree
Hide file tree
Showing 7 changed files with 24 additions and 6 deletions.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ If applicable, add screenshots to help explain your problem.

**Versions**
- OS: [e.g. macos, linux]
- Version [e.g. v0.17.0]
- Version [e.g. v0.18.0]

**Additional context**
Add any other context about the problem here.
3 changes: 1 addition & 2 deletions docs/_advanced/passive_scan.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,5 +43,4 @@ Explanation of Output:
* Extract: This shows where or how the sensitive information is being accessed or used. In this case, it's extracting an x-api-key from the request headers.
* File: Indicates the location of the potential security issue within the codebase, pointing to the exact file and line number where the issue was detected.

This output helps developers immediately identify where and what kind of security issues exist in their code, focusing on passive analysis without actively exploiting the vulnerabilities.
'
This output helps developers immediately identify where and what kind of security issues exist in their code, focusing on passive analysis without actively exploiting the vulnerabilities.
15 changes: 15 additions & 0 deletions docs/_advanced/passive_scan/community_rules.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: Community Rules
parent: Passive Scan
has_children: false
nav_order: 3
layout: page
---

Community rules are managed in several repositories below. You can clone these repositories to the default rule path for use.

To clone the `noir-passive-rules` repository to the default rule path, use the following command:

```bash
git clone https://github.com/owasp-noir/noir-passive-rules ~/.config/noir/passive_rules/
```
4 changes: 4 additions & 0 deletions docs/_includes/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,10 @@ FLAGS:
--no-color Disable color output
--no-log Displaying only the results

PASSIVE SCAN:
-P, --passive-scan Perform a passive scan for security issues using rules from the specified path
--passive-scan-path PATH Specify the path for the rules used in the passive security scan

TAGGER:
-T, --use-all-taggers Activates all taggers for full analysis coverage
--use-taggers VALUES Activates specific taggers (e.g., --use-taggers hunt,oauth)
Expand Down
2 changes: 1 addition & 1 deletion shard.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Project Metadata
name: noir
version: 0.17.0
version: 0.18.0
authors:
- hahwul <[email protected]>
- ksg97031 <[email protected]>
Expand Down
2 changes: 1 addition & 1 deletion snap/snapcraft.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: noir
base: core20
version: 0.17.0
version: 0.18.0
summary: Attack surface detector that identifies endpoints by static analysis.
description: |
Noir is an open-source project specializing in identifying attack surfaces for enhanced whitebox security testing and security pipeline.
Expand Down
2 changes: 1 addition & 1 deletion src/noir.cr
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ require "./options.cr"
require "./techs/techs.cr"

module Noir
VERSION = "0.17.0"
VERSION = "0.18.0"
end

# Print banner
Expand Down

0 comments on commit c2c4e15

Please sign in to comment.