what's the 'f' about recon-ng

[cam-barts]

Hi @yodatron, it sounds like you are removing the f-strings. They are new to python 3.6, and require 3.6 or later to work.

[yodatron]

ah....ok...uh...would this affect the modules? When I moved to the new repo and reinstalled I ran 'ls -a' in recon-ng dir and the data and modules files that were in the bitbucket repo did not show up in the github clone so the problem there was prior to the f-string removal, so I doubt it.

[cam-barts]

No, this would not affect the modules. The modules have been separated into their own repository, located here. Its best to just clone that into .recon-ng.

[yodatron]

ok...thanks a lot...it's been a while since I have had to do this...trying to rebuild somethings that I lost on another distro until I can get that issue fixed...so a lot of this is like having to learn over again....

[lanmaster53]

No, this would not affect the modules. The modules have been separated into their own repository, located here. Its best to just clone that into .recon-ng.

This is actually the wrong approach. The marketplace for installing modules is built into recon-ng. Check out the marketplace command for installing modules. The framework comes with none installed. The wiki has all of this information there along with a video that talks about the differences.

[yodatron]

Hey, just got all the emails on this issue....Thanks, I will try this again.

…

On Sat, Aug 24, 2019 at 2:21 PM lanmaster53 ***@***.***> wrote: No, this would not affect the modules. The modules have been separated into their own repository, located here <https://github.com/lanmaster53/recon-ng-marketplace>. Its best to just clone that into .recon-ng. This is actually the wrong approach. The marketplace for installing modules is built into recon-ng. Check out the marketplace command for installing modules. The framework comes with none installed. The wiki has all of this information there along with a video that talks about the differences. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#9?email_source=notifications&email_token=AMFBYDY4NFYGPYKDJIXJIXLQGF34DA5CNFSM4IN5IJH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CFDLY#issuecomment-524571055>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMFBYD5K46PR6KA4NNFVPI3QGF34DANCNFSM4IN5IJHQ> .