Update credentials.md #869
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rephrased some sentences (trying to not change the message) and removed some spelling mistakes.
MrSeccubus
requested changes
Nov 20, 2024
|
|
||
| ### Does it help? | ||
|
|
||
| Lots of credentials are from so called [combo lists](https://scirge.com/glossary/combo-list). Credentials from different breaches, combined, traded and often of low quality. Most of the time these lists only contain a username and password and are devoid of any context like when the the credentials were "harvested", which platform, service or system they initially belonged to and where the breach occured. | ||
| Lots of credentials are from so-called [combo lists](https://scirge.com/glossary/combo-list). These lists combine credentials from different breaches, are traded, and are often of low quality. Most of the time, these lists only contain a username and password and are devoid of any context, like when the credentials were "harvested," which platform, service, or system they initially belonged to, and where the breach occurred. |
There was a problem hiding this comment.
Suggested change
| Lots of credentials are from so-called [combo lists](https://scirge.com/glossary/combo-list). These lists combine credentials from different breaches, are traded, and are often of low quality. Most of the time, these lists only contain a username and password and are devoid of any context, like when the credentials were "harvested," which platform, service, or system they initially belonged to, and where the breach occurred. | |
| Lots of credentials are from so-called [combo lists](https://scirge.com/glossary/combo-list). These lists combine credentials from different breaches, are traded, and are often of low quality. Most of the time, these lists only contain a username and password and are devoid of any context, like when the credentials were "harvested", which platform, service, or system they initially belonged to, and where the breach occurred. |
Ik vind die comma raar staan binnen de quotes, ligt dat aan mij?
There was a problem hiding this comment.
De comma staat daar om de leesbaarheid van te verbeteren. Zonder de comma klopt de zin niet meer
There was a problem hiding this comment.
Dat snap ik maar dan schrijf je toch ”harvested”, ipv ”harvested,”
There was a problem hiding this comment.
Het lukt mij niet om het pull request aan te passen, kan jij dat doen eventueel @MrSeccubus ?
There was a problem hiding this comment.
#894
PR staat open om het op te lossen
Deze PR is al merged
Feedback van Frank verwerkt.
JstRelax
requested changes
Nov 22, 2024
Co-authored-by: Stan Plasmeijer <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rephrased some sentences (trying to not change the message) and removed some spelling mistakes.