search

ilektrojohn / creepy

A geolocation OSINT tool. Offers geolocation information gathering through social networking platforms.
http://www.geocreepy.com
GNU General Public License v3.0
1.28k stars 302 forks source link

I can't authorize/I dont know how to #31

Closed DaComeaux closed 10 years ago

DaComeaux commented 11 years ago

What steps do I need to take to authorize Creepy?

I have the program installed and running, but no matter what user I search, Creepy returns 0 location results. It finds tweets, but no locations.

When I press the "authorize" under the twitter tab in settings, nothing happens. I press the button, and nothing happens at all.

What is the pin I'm supposed to enter, and where do I find one? I could not find any reference to this pin in any of the readme's or installation txts. I think in one of these posts the creator mentioned a "log in with twitter" option. DOes that exist, and if so where is it?

jamiekaufmann commented 11 years ago

I just wanted to search myself and am having the same issue. What is this pin im supposed to enter? My system time is correct etc......looks like this guy hasn't been around for two years! He responded 3 months ago but never answered any questions. DELETE!

jamiekaufmann commented 11 years ago

And BTW...I did read the wiki page. When you click authorize...nothing happens. Pop up blockers are all off. Twitter authorization doesn't open up. no pin is given.

ghost commented 11 years ago

same issue here

stephanvierkant commented 11 years ago

Same issue here. Maybe it's because of the outdated API? https://github.com/ilektrojohn/creepy/issues/32

PwnicornDev commented 11 years ago

This is the error:

Traceback (most recent call last):
  File "/usr/bin/creepy", line 515, in button_authorize_twitter
    url = self.oauth.get_authorization_url(True)
  File "/usr/lib/python2.7/dist-packages/tweepy/auth.py", line 103, in get_authorization_url
    raise TweepError(e)
tweepy.error.TweepError: HTTP Error 401: Unauthorized
jkosturko4 commented 11 years ago

having same issue - running v 1.94 on a ubuntu - checked for a bad .conf and also checked system time with rdate

ilektrojohn commented 10 years ago

Close as invalid for now, the soon to be released v1.0 handles this.