digest

What is the difference between HTTP Digest Authentication and SSL from a performance, security and flexibility point of view? The pros and cons of HTTP Digest Authentication are explained quite clearly in the Wikipedia article on the topic -- you should read that! To put it bluntly: HTTP Digest Auth will only protect you from losing your cleartext password to an attacker (and considering the state of MD5 security, maybe not even that). It is however wide open to Man-in-the-Middle attacks and also -- depending on the implementation, since most of the advanced features are optional -- replay,

I'm trying to use the Apache/Jakarta HttpClient 4.1.1 to connect to an arbitrary web page using the given credentials. To test this, I have a minimal install of IIS 7.5 on my dev machine running where only one authentication mode is active at a time. Basic authentication works fine, but Digest and NTLM return 401 error messages whenever I try to log in. Here is my code: DefaultHttpClient httpclient = new DefaultHttpClient(); HttpContext localContext = new BasicHttpContext(); HttpGet httpget = new HttpGet("http://localhost/"); CredentialsProvider credsProvider = new BasicCredentialsProvider();

The Google App Script function computeDigest returns a byte array of the signature. How can I get the string representation of the digest? I have already tried the bin2String() function. function sign(){ var signature = Utilities.computeDigest(Utilities.DigestAlgorithm.MD5, "thisisteststring") Logger.log(bin2String(signature)); } function bin2String(array) { var result = ""; for (var i = 0; i < array.length; i++) { result += String.fromCharCode(parseInt(array[i], 2)); } return result; } but it puts "" in the Logs Mogsdad If we put Logger.log(signature); right after the call to computeDigest()