fuzzdb: Updating the raft lists

[kurobeats]

Updating the raft lists as updates have been made by the SecLists project in the last few years

[kingthorin]

Note this is add-on is specifically based on fuzzDB. If lists are coming from other sources that might cause a sync/maintenance issues.

Assuming this goes ahead the DCO will need to be addressed and the CHANGELOG will need an entry.

[kurobeats]

Note this is add-on is specifically based on fuzzDB. If lists are coming from other sources that might cause a sync/maintenance issues.

Assuming this goes ahead the DCO will need to be addressed and the CHANGELOG will need an entry.

I'm not overly worried about fuzzDB being the source, these particular files haven't been touched by that project in 7 years. On the DCO issue, can I fix that without trashing my existing merge? Happy to update the CHANGELOG, ideally what would you like to see added?

[thc202]

Better to also PR the update in fuzzDB project.

[kingthorin]

The DCO bit is simple:

git commit --amend --no-edit --signoff
git push --force

[kingthorin]

For the CHANGELOG you can add to the unreleased change block, something like Updated RAFT lists based on more recent SecLists contributions.

[thc202]

Could you fix up the commits?

[kingthorin]

Just to keep everyone updated. I have been in-touch with the FuzzDB project owner. He needs to regain access to his GitHub account but is working on addressing the upstream PR and getting us access.

[kurobeats]

Could you fix up the commits?

Apologies, what have I missed with the commit?

[kingthorin]

Please do an interactive rebase and fix-up or squash into a single commit:

• https://www.kernel.org/pub/software/scm/git/docs/git-rebase.html#_interactive_mode
• https://www.instructables.com/id/How-to-Rebase-Interactive-With-Eclipse-eGit/
• https://wiki.eclipse.org/EGit/User_Guide#Interactive_Rebase

[kurobeats]

Hopefully I've done it correctly.

[kingthorin]

Looks like it 🙂

[thc202]

Thank you!