Case-sensitivity in "options" about recon-ng

[lanmaster53]

This is a good point. I remember there being a reason I did this, so I'll have to look back at my notes, but it was years ago and I was probably a bad design decision that could have been fixed another way.

[BBhacKing]

Background:
I only reported this because the behavior has changed in 5.x.

They've always been listed with upper-case names. But in 4.x they could be set in any case. In 5.x, if you get the case wrong, the framework has no idea what you mean and offers no guidance.

Here's 4.9.5:

[recon-ng][default] > set threads 5
THREADS => 5
[recon-ng][default] > set THREADS 12
THREADS => 12
[recon-ng][default] > set threAds 13
THREADS => 13

And here's 5.1.0:

[recon-ng][example] > options set threads 9
[!] Invalid option name.
[recon-ng][example] > options set THREADS 11
THREADS => 11

[lanmaster53]

Interesting. That's something I explicitly changed. Must be something specific to Python 3.