rules
Here are 428 public repositories matching this topic...
-
Updated
Aug 19, 2020 - Python
-
Updated
Dec 2, 2020 - JavaScript
-
Updated
Dec 6, 2020 - C#
-
Updated
Jul 13, 2020 - PHP
-
Updated
Oct 11, 2020 - Shell
-
Updated
Sep 9, 2020 - Clojure
-
Updated
Oct 20, 2020 - Java
-
Updated
Nov 30, 2020 - HTML
-
Updated
Jul 10, 2020
-
Updated
Feb 17, 2020 - Python
You should order masks by efficiency (occurrences/key_space) because this will lead to the less guesses to crack passwords.
Looking at the top 5:
https://github.com/kaonashi-passwords/Kaonashi/blob/5239bd333ed34993b43126a4499606ba70086034/masks/kaonashi_masks_numbered.txt#L1-L5
And ordering just the 1000 in kaonashi_masks_numbered.txt by efficiency the top 5 are now:
673407:?u?u?u?u
-
Updated
Dec 5, 2020 - JavaScript
-
Updated
May 15, 2020 - C#
-
Updated
Jul 28, 2018 - Python
-
Updated
Oct 30, 2020
-
Updated
Dec 3, 2020
-
Updated
Jan 10, 2019 - PHP
-
Updated
Nov 24, 2020 - JavaScript
-
Updated
Dec 6, 2020 - Smarty
-
Updated
Jul 1, 2020 - Java
Improve this page
Add a description, image, and links to the rules topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the rules topic, visit your repo's landing page and select "manage topics."


Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase
Expected behavior:
to be able to insert to a sql database in an activity
What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database
Additional information you deem important (e.g. I need this tomorrow):