Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Conversation

SebieF
Copy link
Contributor

@SebieF SebieF commented Sep 11, 2020

  • Added ncrack Authentication Scanner and integration test

Missing:

  • Option to mount user and password files into scan (dependent on change in operator)
  • Example for wordpress or MySQL

@SebieF SebieF added the enhancement New feature or request label Sep 11, 2020
@SebieF SebieF requested a review from nigthknight September 11, 2020 13:46
@SebieF SebieF self-assigned this Sep 11, 2020

parser/
scanner/
examples/
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

- -v
- --user=root,admin
- --pass=THEPASSWORDYOUCREATED,12345
- ssh://dummy-ssh
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

@@ -0,0 +1 @@
node_modules/
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

@@ -0,0 +1 @@
node_modules/
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

<address addr="45.33.32.156" addrtype="ipv4"/>
<port protocol="tcp" portid="80" name="http"></port>
</service>
</ncrackrun>
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub


scannerJob:
resources: {}
# scannerJob:
Copy link
Member

Choose a reason for hiding this comment

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

Is there a reason these lines have to be commented out?

Copy link
Member

Choose a reason for hiding this comment

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

This is done in all scanners and recommended by helm.
Basically don't impose resource restrictions by default but give users the ability to configure them on their own.

);
},
3 * 60 * 1000
);
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

},
]
`);
});
Copy link
Member

Choose a reason for hiding this comment

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

This file should end with a newline as recommended by GitHub

"description": "Parses result files for the type: 'ncrack-xml'",
"main": "",
"scripts": {},
"keywords": [],
Copy link
Member

Choose a reason for hiding this comment

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

Should we define some useful keywords?

protocol: protocol,
service: portName,
username,
password,
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure if we should include the password.

Copy link
Member

Choose a reason for hiding this comment

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

I think this needs to be in here because otherwise you can't really confirm that it was properly identified.
But its probably a good idea to write this in the docs for ncrack that users need to consider this.

@nigthknight nigthknight self-requested a review September 18, 2020 12:11
@SebieF SebieF merged commit 6ac36be into master Sep 18, 2020
@J12934 J12934 deleted the ncrack branch September 18, 2020 13:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants