tgotwig / homebrew-feroxbuster

Who is Thomas Gotwig? 🤔

Hellooo there! 👋 I'm a passioned programmer with background in Bioinformatics from my Bachelor study 👨‍🎓 Interested in topics such as Full-Stack-Development, DevOps and Life-Sciences 🧑‍💻

⚡️ Recent activities

1. 🗣 Commented on #47 in tgotwig/vidmerger
2. 🔒 Closed issue #26 in tgotwig/vidmerger
3. 🗣 Commented on #46 in tgotwig/vidmerger
4. 🎉 Merged PR #45 in tgotwig/vidmerger
5. 🎉 Merged PR #5 in tgotwig/homebrew-linux-vidmerger

💻 Hardware

• 💻 MacBook Air (M1, 2020)
• 📺 Apple Studio Display
• ⌨️ Apple Magic Keyboard (US)
• 🏗️ Flexispot standing converter

💿 Software

• MacOS
• Paste
• Safari
• DeepL
• ForkLift
• Obsidian
• ChatGPT
• GitKraken
• Luminar AI
• Warp Terminal
• Microsoft To Do
• Visual Studio Code
• Affinity Photo & Designer
• Parallels Desktop & Toolbox

🤓 Dev Links 👉 Chocolatey | Dev | Observable | Stackoverflow | Vagrantup

🍻 Social Links 👉 LinkedIn

homebrew-feroxbuster's Issues

Add ferox-config.toml to installation

closes #1

The current installation does not place the ferox-config.toml anywhere on the filesystem. The .deb places it in /etc/feroxbuster, as it's expected to be executed with root permissions.

My thought is to copy it into the config directory that the library used in feroxbuster points to on a mac (https://docs.rs/dirs/3.0.1/dirs/fn.config_dir.html).

I've already done similar with the linux version, and all seems to work as expected.

This is in response to, and closes, this issue.

👷 Add to Homebrew-Core

Hey Thomas! 👋

I saw your contribution to Feroxbuster, and as the RustScan core dev I thought I'd show you something helpful.

I spent a good while on the homebrew-core formula, so feel free to copy it for Feroxbuster.

class Rustscan < Formula
  desc "Modern Day Portscanner"
  homepage "https://github.com/rustscan/rustscan"
  url "https://github.com/RustScan/RustScan/archive/1.10.0.tar.gz"
  sha256 "63c387c645826107734eb10d45b0a540a69fb3a61e478593f515adce95bad530"
  license "GPL-3.0-or-later"

  bottle do
    cellar :any_skip_relocation
    sha256 "3f6072b555545a3efe33cc84aec3ba11c8110b038fe51cd1ec95be921e44fe16" => :catalina
    sha256 "29b494ff1b888b9cd2e94a61168236ccab5a2030a923efc490706301dcfe7bef" => :mojave
    sha256 "03b01fce247218e8dd5e60565199c61e4d458ab0d66f9952a2bbf158d04c9f0f" => :high_sierra
  end

  depends_on "rust" => :build
  depends_on "nmap"

  def install
    system "cargo", "install", *std_cargo_args
  end

  test do
    assert_no_match /panic/, shell_output("#{bin}/rustscan --greppable 127.0.0.1")
    assert_no_match /panic/, shell_output("#{bin}/rustscan --greppable 0.0.0.0")
  end
end

The tests run by grepping the output for the regex /panic/. So if the Rust program doesn't panic, it's a-okay!

Not sure on how much you know about core, so I'll share a few things:

• Project must be 30 days or older, and used by people (I can confirm that Ferox is, it's very popular in TryHackMe right now)
• You must follow this very long process
• The format of the ruby file must be the same. One newline out of place and CI fails. If the order of items is different (license before sha256) and CI fails. They're very picky about this.

Other than that, good luck if you choose to contribute to core! Feel free to ping me in a PR if you need any more help 😄