Restricting api.twitter.com to SSL/TLS traffic

newsytweets · 2014-01-14T23:20:32.000Z

@cornel74 you are a lifesaver! Thanks.

stephenemo · 2014-01-15T00:24:17.000Z

All nodejs modules are broken today including ntwitter

https://github.com/AvianFlu/ntwitter/blob/master/lib/twitter.js

See it using http and seen an option for secure. Could do with more samples here

twit = new twitter({
consumer_key: ,<— FILL ME IN
consumer_secret:, // <— FILL ME IN
access_token_key: <— FILL ME IN
access_token_secret: , // <— FILL ME IN
secure: true
});

Also filled in callback url and sign in with twitter. Still getting error
"My error: Error: socket hang up: undefined"

Trying the one listed on twitters site https://github.com/aivis/user-stream

startweetmobile · 2014-01-15T03:08:10.000Z

Im still getting 403s for oauth/authorize calls and I am using the https endpoint. Any one else still having issues?

evasori_info · 2014-01-15T04:25:38.000Z

Maybe an even better solution is to add

ssl => 1

to the Net::Twitter (or derived) constructors, so that SSL/TLS will be used for all connections irrespective of default API URL.

michichan · 2014-01-15T04:49:08.000Z

When I do that, I am getting
500 Can’t connect to api.twitter.com:443 (Crypt-SSLeay can’t verify hostnames)

VapersPlace · 2014-01-15T05:16:55.000Z

This fixed my issue. Thanks.

Al_Sweetman · 2014-01-15T09:12:19.000Z

Well, it is kind of related? To quote: "If your application still uses HTTP plaintext connections you will need to update it to use HTTPS connections, otherwise your app will stop functioning. "

From what I can see, the http://stream.twitter.com/1.1 has now been “turned off” as part of this change, hence causing all instances of hosebird to fail? This is hosebird that fails, rather than our individual application.

aldnet · 2014-01-15T10:41:55.000Z

And my question now that we solved the problem yesterday when we detect the change. Why does not communicate this change by common channels like Announcements here in the discussions, or in the dev blog?

I think it’s an important and critical change and only announcing in this section for my is not the right way, imho.

MarshallCape · 2014-01-15T11:12:33.000Z

I see the normal Twitter widget and even Facebook Like Box not showing up in Firefox, Safari and latest IE11 for windows 7 anymore but is in the latest Chrome. Is the normal Twitter widget which shows normal posts etc affected by this SSL connection? I’m trying to see if i’m doing something wrong on my website for this to not be showing anymore?!

MikeSouthern · 2014-01-15T11:22:52.000Z

That sucks. I just have a tiny perl script that I use for sending single news headline tweets a couple of times a day. You’d think that for such simplicity the goal would be to keep it simple.

roscoe_tom · 2014-01-15T11:33:44.000Z

I was so positive that I had no http connections left. Turns out I was wrong, changed one line and we’re good to go.

lfcipriani · 2014-01-15T11:41:01.000Z

We announced at @twitterapi, Discussion forum and Calendar. Even so, we are improving our developer communications to ensure developers are aware of all important changes.

RegardingBTC · 2014-01-15T12:36:03.000Z

Problem solved, thanks!

MuneebZulfee · 2014-01-15T12:50:12.000Z

I have a .net wrapper which tweets, the problem im facing is that i can get the followers but cannot tweet, its returning 403

ripldev · 2014-01-15T13:38:08.000Z

I am using Twiiter4j 3.0.3 ans till getting issue

michichan · 2014-01-15T13:45:06.000Z

I got it to work… In addition to adding the
apiurl => 'https://api.twitter.com/1.1’
I also had to add…
$ENV{‘PERL_LWP_SSL_VERIFY_HOSTNAME’} = 0;
and that seems to work.

misbar2022 · 2014-01-15T15:39:36.000Z

i tried this with twitter4j 3.0.3 configurationBuilder.setUseSSL(true); and it doesn’t work :S any ideas anyone

peremestresTILD · 2014-01-15T16:39:11.000Z

configurationBuilder.setUseSSL(true); works for me! Thank!

ConfigurationBuilder configurationBuilder = new ConfigurationBuilder();
configurationBuilder.setOAuthConsumerKey( Constants.TWITTER_CONSUMER_KEY);
configurationBuilder.setOAuthConsumerSecret(Constants.TWITTER_CONSUMER_SECRET);
configurationBuilder.setUseSSL(true);
Configuration configuration = configurationBuilder.build();
twitterFactory = new TwitterFactory(configuration);
twitter = twitterFactory.getInstance();

fmaguin · 2014-01-15T16:38:38.000Z

I am using Twitter4j 3.0.3 too and it works with SSL.
Adding configurationBuilder.setUseSSL(true) (or http.useSSL=true in my case as I am using a properties file) is one part of the solution.

If you’re having an exception like “sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target”, you need to update your certificates.
I used the root certificates from VeriSign (see https://dev.twitter.com/docs/security/using-ssl) to update mines and the problem was solved.

HTH.

The405radio · 2014-01-15T17:06:39.000Z

Any options other than installing an SSL certificate on my entire site (for this one purpose)?