Hi,

I am sincere thanks to all twitter engineers..

Special thanks to Cameron Kaisor and John Adams.

Thanks for the valuable inputs. I updated the crypto library with new
version and the problem got fixed.

Once again, I am thanks to all twitter engineers.

Regards,
George





On Wed, Dec 1, 2010 at 12:08 PM, Cameron Kaiser <[email protected]>wrote:

> > > > _Info: error:140D108E:SSL
> routines:TLS1_CHANGE_CIPHER_STATE:compression
> > > > library error_
> > >
> > > This suggests a problem in your crypto library, or less likely zlib.
> >
> > I dont understand about crypto libray or less likely zlib...
> >
> > Could u please give a description for this. What do this for twitter ?
>
> This is getting off-topic for this list, but in brief, this refers to your
> cryptographic library which is being used to handle the encryption and
> decryption to Twitter's SSL server. zlib refers to the specific compression
> library your system likely uses (and you will note that this is referenced
> in the error above). Many crypto libraries use zlib. You should make sure
> that your cryptographic software, such as NSS or OpenSSL, passes all of its
> built-in self-tests such as by running 'make test' in the source directory
> for your crypto distro. If it doesn't work, SSL through libcurl won't
> either.
>
> If you're still not sure what this is, you probably should be referring to
> the libcurl documentation for more. libcurl can use either NSS or OpenSSL.
>
> --
> ------------------------------------ personal:
> http://www.cameronkaiser.com/ --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
> [email protected]
> -- You can't kill me because I've got magic aaargh. -- Terry Pratchett
> --------
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to