honeynet / honeynet.org Goto Github PK

Need to create jekyll layouts for the following types:

• pages
• posts (blog posts)

• how to add a blog post
• adding a page
• making changes to the site (in general)

~ usual fun

Need to add a way to check for broken links on the site. These checks should be done on all pushes and PR requests.

This should be a relatively straightforward port. We can update the BoD on the way. 😅

This is maybe the most major undertaking - how many old blog posts do we want to migrate, and can we do it automatically? @xandfury, any thoughts? :)

The blog post export current does not include author names. It would be splendid if would simply scrape those and re-add to the yaml files. Not talking about pictures, bios, or anything, just the plain author names.

Sidebar(s) from the site need to be re-factored into re-usable components.

In Safari (desktop and mobile) the text of the buttons is not displayed correctly. It should be centered along the margins maybe with a smaller font.

I've imported all pages up to 2022.
I have not updated the menu. It could be done manually in the hugo.toml or we find an automated way using the folder structure.
We need to import 2023.
Seems like many years are missing the ideas pages 😕

I'm honestly not sure if this page provides any value as it is. Shall we perhaps keep it off the site until a need arises? Or is there a particular use case for now? :)

In a first version I propose we just do a more-or-less verbatim copy of https://www.honeynet.org/projects/. Eventually we maybe get around to displaying progress / activity from GitHub. :)

All the posts and pages have been converted to markdown, in jekyll format. They currently sit in the development branch. The page export works pretty well. However, we still would need to think about wp-contents, and how we want to accommodate that into the site.

At first, I wanted to commit the entire directory into the repo. But soon realised that we can probably prune a lot of contents from there. I also faced some git corruption issues like so:

[development a335a2d] remove wp-content
error: inflate: data stream error (invalid stored block lengths)
fatal: packed object e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 (stored in .git/objects/pack/pack-9a11e7fc3c38c0534b748b57ad56c2671e0514d7.pack) is corrupt

We do need the essential bits on the site. Rest we can probably keep into to a separate repo (and add references) - pretty much like forensic challenges. 🙂

Creating re-usable components such as headers and footers.

The Glutton blog post (https://www.honeynet.org/2023/09/23/glutton-1.0/) renders badly on mobile. Let's figure out why and fix it.

Maybe we have a GitHub activity feed here?

Could be done using https://gohugo.io/templates/data-templates/#get-remote-data

Add a scheduled GitHub action to recreate the page.

Integration between GitHub and Twitter/Bluesky/...

Make sure RSS feed is functional and on the same URL as our current

@dpisano will shift over DNS some point today. Once #35 is done, I'll notify all@ that...

1. We have a new website
2. If we missed some projects on https://honeynet.github.io/projects/, they should add them.
3. If they want a fancy authors page (#34), they should create their own profile.

I've already migrated the header, but it needs a bit of content below it. The current front page has some stuff that does not make a ton of sense to me. If no-one objects, we should maybe just replace it with news teasers?

@glaslos: any opinions on what to do here? Those are all super super old obviously. So we could maybe add a note that the project used to publish papers, and then keep them for historic purposes?

It looks like we are missing the companies that are sponsoring our work from the funding page. We had this on the old website.

...and make it sticky. Just needs to say that we're having a workshop again (yay!) and point to https://denmark2024.honeynet.org/. :)

This is super super straightforward. If you, dear reader of this issue, want to get your hands dirty, it's a fantastic first contribution. 😃 🍰

This should have some placeholder profile picture. Here's the associated event:

{
  "id": "30896298962",
  "type": "ReleaseEvent",
  "actor": {
    "id": 41898282,
    "login": "github-actions[bot]",
    "display_login": "github-actions",
    "gravatar_id": "",
    "url": "https://api.github.com/users/github-actions[bot]",
    "avatar_url": "https://avatars.githubusercontent.com/u/41898282?"
  },
  "repo": {
    "id": 519832,
    "name": "mitmproxy/mitmproxy",
    "url": "https://api.github.com/repos/mitmproxy/mitmproxy"
  },
  "payload": {
    "action": "published",
    "release": {
      "url": "https://api.github.com/repos/mitmproxy/mitmproxy/releases/115087111",
      "assets_url": "https://api.github.com/repos/mitmproxy/mitmproxy/releases/115087111/assets",
      "upload_url": "https://uploads.github.com/repos/mitmproxy/mitmproxy/releases/115087111/assets{?name,label}",
      "html_url": "https://github.com/mitmproxy/mitmproxy/releases/tag/10.0.0",
      "id": 115087111,
      "author": {
        "login": "github-actions[bot]",
        "id": 41898282,
        "node_id": "MDM6Qm90NDE4OTgyODI=",
        "avatar_url": "https://avatars.githubusercontent.com/in/15368?v=4",
        "gravatar_id": "",
        "url": "https://api.github.com/users/github-actions%5Bbot%5D",
        "html_url": "https://github.com/apps/github-actions",
        "followers_url": "https://api.github.com/users/github-actions%5Bbot%5D/followers",
        "following_url": "https://api.github.com/users/github-actions%5Bbot%5D/following{/other_user}",
        "gists_url": "https://api.github.com/users/github-actions%5Bbot%5D/gists{/gist_id}",
        "starred_url": "https://api.github.com/users/github-actions%5Bbot%5D/starred{/owner}{/repo}",
        "subscriptions_url": "https://api.github.com/users/github-actions%5Bbot%5D/subscriptions",
        "organizations_url": "https://api.github.com/users/github-actions%5Bbot%5D/orgs",
        "repos_url": "https://api.github.com/users/github-actions%5Bbot%5D/repos",
        "events_url": "https://api.github.com/users/github-actions%5Bbot%5D/events{/privacy}",
        "received_events_url": "https://api.github.com/users/github-actions%5Bbot%5D/received_events",
        "type": "Bot",
        "site_admin": false
      },
      "node_id": "RE_kwDOAAfumM4G3BcH",
      "tag_name": "10.0.0",
      "target_commitish": "main",
      "name": "mitmproxy 10.0.0",
      "draft": false,
      "prerelease": false,
      "created_at": "2023-08-04T09:37:11Z",
      "published_at": "2023-08-04T09:37:12Z",
      "assets": [],
      "tarball_url": "https://api.github.com/repos/mitmproxy/mitmproxy/tarball/10.0.0",
      "zipball_url": "https://api.github.com/repos/mitmproxy/mitmproxy/zipball/10.0.0",
      "body": "Changes: See [CHANGELOG.md](https://github.com/mitmproxy/mitmproxy/blob/main/CHANGELOG.md).\n\nYou can find the latest release packages at https://mitmproxy.org/downloads/.\n",
      "short_description_html": "<p>Changes: See <a href=\"https://github.com/mitmproxy/mitmproxy/blob/main/CHANGELOG.md\">CHANGELOG.md</a>.</p>\n<p>You can find the latest release packages at <a href=\"https://mitmproxy.org/downloads/\" rel=\"nofollow\">https://mitmproxy.org/downloads/</a>.</p>",
      "is_short_description_html_truncated": false
    }
  },
  "public": true,
  "created_at": "2023-08-04T09:37:13Z",
  "org": {
    "id": 4652787,
    "login": "mitmproxy",
    "gravatar_id": "",
    "url": "https://api.github.com/orgs/mitmproxy",
    "avatar_url": "https://avatars.githubusercontent.com/u/4652787?"
  }
}

Was thinking that we should have a general information gsoc page on the site with discord invite link and ideas. GSoC year pages should contain ideas for that year and results/reports.

Thoughts? :-)

List of historic projects, separate into maintained and unmaintained. Could be based on last GitHub commit.

There are some officially supported plugins we can look at. For e.g:

https://import.jekyllrb.com/docs/wordpress/

Maybe once the site is up, we would need to add a service for client side attacks. This would depend on how we would like to use the site though.

We currently use the standard routing based on menu item + content folder. This is not matching what we used to have.

See https://gohugo.io/content-management/urls/#url on how to modify

Legacy:
honeynet.org/2022/10/06/gsoc-2022-project-summary-creating-playbooks-for-intelowl/

Current Hugo:
honeynet.org/blog/2022-10-06-gsoc-2022-project-summary-creating-playbooks-for-intelowl/

What needs to be done:

• Move all blog posts into a yyyy/mm/dd folder structure
• Removed the blog/ prefix from the path

Try this:

# Remove the "/posts/", "/categories/", "/tags/" prefixes from URLs.
permalinks:
    posts: '/:filename/'
    categories: '/:slug/'
    tags: '/:slug/'

The live site (https://www.honeynet.org/challenges/) is currently quite broken - while all the challenge sub-pages exist, the download links all don't work. However, @xandfury collected them all over at https://github.com/honeynet/forensic_challenges. 🍰 So as part of the migration (however it may look), we should make sure to prominently link to that repo. 😃

Need to switch from "build from branch" to deploy with github actions. All tests should pass before the site is deployed. It's fine right now since we're in very early stages of development.

Everyone I've talked to seems to be in agreement about making the website repo public, so let's do it! If you think that's a bad idea, here is your place to speak up in the next 24 hours.

• I don't know what's in the old branches/issues. @dpisano mentioned a members list page on the old website we probably don't want to expose. To avoid all of this, I'd just create a new honeynet.org repo, copy over the v2 branch as the new main branch there, and that's it.
• For all information that we don't want to expose publicly, https://github.com/honeynet/docs is the right place. @hgascon and others have done an amazing job there so far. 🎉