Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New name for go-ftw #312

Open
theseion opened this issue Jun 5, 2024 · 10 comments
Open

New name for go-ftw #312

theseion opened this issue Jun 5, 2024 · 10 comments

Comments

@theseion
Copy link
Collaborator

theseion commented Jun 5, 2024

We have been thinking about renaming the project. The name go-ftw was a quick win to replace the retired ftw.

Our reasons to rename the project are:

  • go prefix isn't meaningful to users in any way
  • the meaning of ftw is not obvious (it is "framework for testing WAFs")
  • we like our command line utilities to have short names that are easy to type

Candidates

Legend:

  • 🚫: rejected

waft 🚫

Meaning: "WAF tester"

Pros:

  • short, easy to type
  • memorable
  • English word
  • meaningful

Cons:

  • "waft" has a mostly negative connotation

westy

Meaning: "Web Server Test utilitY"

Pros:

  • short, easy to type
  • memorable
  • almost an English word

Cons:

  • not immediately recognisable as WAF or test related

waffles, waflz, etc. 🚫

Cons:

  • name taken by WAFLZ

wtf

Meaning: "WAF testing framework"

Cons:

  • wtf... ;)
@RedXanadu
Copy link
Member

RedXanadu commented Jun 6, 2024

For what it's worth, I think the current name is fine and I've always known what FTW stood for (it's stated on the first line on the front page / readme file of both go-ftw and the original ftw. I wasn't aware this was unknown / an issue. If someone will not read the first line of your project then that's a them problem, not a you problem 😛)

But, always happy to make alternative name suggestions 😀

Of the suggestions so far:

  • +1 to wtf
  • westy is a nice name, but I also fear it's not specific enough / doesn't mention WAFs

wafer

Web Application Firewall EvaluatoR

Web Application Firewall Evaluation Routine

Web Application Firewall Evaluation Runner 😀 (◀️ I particularly like this one!)

Web Application Firewall Evaluation Runtime

Web Application Firewall ExerciseR 😅

Web Application Firewall Exercise Routine

Web Application Firewall Evaluating Robot 🤖


aft

Application Firewall Tester


after

Application Firewall TestER


taft

The Application Firewall Tester


rafter

(The) Reliable Application Firewall TestER 😅


lafter

Layer 7 Application Firewall TestER

@theseion
Copy link
Collaborator Author

theseion commented Jun 7, 2024

These are great, thanks! I had wafr in my head but couldn't come up with a good explanation for the acronym.

@fzipi
Copy link
Member

fzipi commented Jun 7, 2024

raft

Real Application Firewall Tester

@theseion
Copy link
Collaborator Author

theseion commented Jun 7, 2024

Yeah, unfortunately, raft is taken by the raft protocol.

@huberts90
Copy link
Collaborator

Let me add adding my two cents:

  1. WAFIn: Web Application Firewall Inspector
  2. WAFEx: Web Application Firewall Examiner
  3. WAFOver: Web Application Firewall Overseer

@fzipi
Copy link
Member

fzipi commented Jun 21, 2024

Waf Testing Helper: wth!

@dune73
Copy link
Member

dune73 commented Jun 21, 2024

Please pronounce phonetically.

@fzipi
Copy link
Member

fzipi commented Jun 21, 2024

Please pronounce phonetically.

ppp?

@theseion
Copy link
Collaborator Author

wth is actually a fun idea. It could also stand for what the heck, which would be a funny little insider :)

@RedXanadu
Copy link
Member

RedXanadu commented Jul 17, 2024

Still not convinced a new name is needed or necessarily a good idea, but if we just want a new short command to type that isn't 'ftw', and we want to distinguish the old ftw from the "new" ftw, how about:

nftw

New FTW / New Framework for Testing WAFs

"Not FTW"

"Next FTW"

Or keep it ambiguous, and the "n" doesn't officially stand for anything:

"n" FTW / "n" Framework for Testing WAFs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants