Flickr api key option

Issue #189 closed
JohnnyAMD
created an issue

Hi,

I'm using recon-ng v4.7.3.

Flickr API is identified by key : secret combination.

Recon-ng is asking only for flickr_api value which under described situation is not quite right.

Please advise.

PS.

Also, I'm not too sure how jigsaw / pwnedlist api options are still beneficial as far you have to pay a a LOT of money to be subscribed to their service.

Cheers,

-Johnny

Comments (12)

  1. Tim Tomes repo owner

    Has the Flickr API changed? This still works for me. Perhaps there is an older API that the module is based on.

    As far as Jigsaw and PwnedList go, Jigsaw no longer provides API keys and yes, PwnedList is very expensive, but these modules are extremely useful for those of us that have access.

  2. Tim Tomes repo owner

    I believe you are getting the keys for the new API. The module leverages the legacy API. It's been years since I did it, so I don't remember the process of getting an API key. Maybe it's the key? Have you tried them both? Do either work? If you figure this out, let me know and I'll update the wiki. Thanks.

  3. catalpa88

    Hello, I'm was having the same issue with v4.9.0 on Kali. The flickr_api should use the key vs. the secret.

    I tested it directly with a URL in the browser, and that works for me, but with the flickr module, it is saying invalid key format as well. I built the test URL using the API explorer at: https://www.flickr.com/services/api/explore/flickr.photos.search

    The URL that it generated is: https://api.flickr.com/services/rest/?method=flickr.photos.search&api_key=my_32_char_key&user_id=&lat=61.1069017&lon=-149.8090285&radius=1&format=json&nojsoncallback=1

    Now, as I was typing this post, I exited recon-ng to go back in and debug, I'm just getting started and in my first hours of using it, so I wasn't sure if it used -v switch or something. I loaded it, set VERBOSITY to 2, loaded the workspace that I had been using, loaded the flickr pushpin, hit run, and it ran. no problem...Maybe there is something with where the key is accessed that causes an issue if the module is run when there is not a key or if recon-ng hasn't been started while having the key already entered? I wish I was paying more attention...Hopefully this is helpful.

  4. rick

    Hi, thanks. I don't know what the heck I did wrong earlier, but It's working for me now.

    v 4.9.2 confirmed working with flickr_api set to key, NOT secret. Thanks

  5. mphillips777

    I loaded it, set VERBOSITY to 2, loaded the workspace that I had been using, loaded the flickr pushpin, hit run, and it ran. no problem...Maybe there is something with where the key is accessed that causes an issue if the module is run when there is not a key or if recon-ng hasn't been started while having the key already entered? I wish I was paying more attention...Hopefully this is helpful.

    This is precisely it. I ran into this issue using recon-ng inside a Kali 32-bit vmware image. Got my API key, entered it with "keys load," suspended session. When I reloaded the session and tried to run the flickr module, it rejected the request with "[!] Invalid API Key (Key has invalid format)."

    "reload", "use recon/locations-pushpins/flickr", "run" — works flawlessly.

    I found this via Google, so I want to draw attention to the solution catalpa88 suggested above.

  6. Tim Tomes repo owner

    Very interesting. I'm not able to replicate the issue. I wonder if something in the underlying operating system is caching the keys in memory and when you cycle the VM or something it gets lost... Anyway, thanks all.

  7. Log in to comment