Migrate Favicon DB Content

[kingthorin]

https://wiki.owasp.org/index.php/OWASP_favicon_database is referenced by https://tryhackme.com/room/contentdiscovery

we should migrate it to the new site.

[HimanshHK]

Hello Sir, I am Himanshu. I am interested to work on this. Can you please assign me this.

[kingthorin]

It would probably been a good move to implement this as a data file with a template/include. That way maintenance will be easier.

For an example check the api-tools yaml and html in the repo.

[HimanshHK]

Sure Sir, I will do it as fast as possible.

…

On Sat, Jan 14, 2023 at 12:21 AM Rick M ***@***.***> wrote: It would probably been a good move to implement this as a data file with a template/include. That way maintenance will be easier. For an example check the api-tools yaml and html in the repo. — Reply to this email directly, view it on GitHub <#684 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXSTOVGQ73FB3UXSU5J4MZTWSGPZXANCNFSM6AAAAAAS5UOAQI> . You are receiving this because you were assigned.Message ID: ***@***.***>

[HimanshHK]

Sir, I am not getting what's actually the issue here. Can you please explain that and will you please tell me how to run the project?

[kingthorin]

That was covered in earlier comments. Migrate the content from the old wiki, into a data file and applicable display components (similar to api-tools already in this repo).

Info on local testing can be found here: https://owasp.org/migration/ (toward the bottom of the page).

[kingthorin]

@HimanshHK do you still intend to tackle this?

[nikhil25803]

Hey @kingthorin | Can you assign me this?
Would love to work on this

[nikhil25803]

As read earlier in the comments, referencing from api-tools.yml. On the webpage we have a favicons database such as 6399cc480d494bf1fcd7d16c42b1c11b:penguin.
So what should I name this the respective .yml file I'll create
Eg.

- name: "penguin"
  id: "6399cc480d494bf1fcd7d16c42b1c11b"

Is this good to go?

[kingthorin]

Maybe include an algorithm field, (those on the old wiki are MD5 I believe), as well as a source field (start with "owasp_wiki" for those? 🤷‍♂️). That way in the future if we have new entries with SHAs or other hashes we can differentiate, and for posterity we also know where things came from.

Also you'll have to create a new template like: https://github.com/OWASP/www-community/blob/08bbc8291cf9b4b40d0df7ad1efd74693b598ec8/_includes/api-tools.html
and a new place for it to be used like: https://github.com/OWASP/www-community/blob/08bbc8291cf9b4b40d0df7ad1efd74693b598ec8/pages/api-security-tools.md?plain=1

[kingthorin]

There are some more entries and sources here that you could add as well: https://vulners.com/openvas/OPENVAS:136141256231020108

[nikhil25803]

Understood, will update you soon with the PR :)