Some corporate networks are behind HTTP proxy servers that use NTLM authentication. Dropbox currently doesn’t support this kind of proxy authentication. However, some users have reported some success using an intermediate proxy, such as [WayBack] NTLMAPS or [WayBack] cntlm, to get Dropbox running on their network.
[Archive.is] Dixin’s Blog – Use Fiddler with Node.js Fiddler is an useful HTTP proxy debugger on Windows. It would be nice if it can work with Node.js applications. To do this, just need to proxy Node.js requests through Fiddler… on port 8888.
By default, Chrome uses the same proxy server as Internet Explorer: the system one that your Chrome settings page accesses from chrome://settings/search#proxy through this command-line call:
Copy had some advantages and disadvantages. For instance, it was better handling long file names, character encodings in filenames and a lot easier to configure over a CNTLM proxy than DropBox, but unlike DropBox didn’t keep history of changes.
Note that Mover has many more connectors, including cloud storage ones (Box, Copy, Dropbox, Google Drive, OneDrive and Yandex.Disk are free):
[WayBack] Connectors • Mover: FTP, Dropbox, Box, GoogleDrive, Copy, Egnyte, Amazon S3, SharePoint, MySQL the list goes on!
For me it means it’s time to think about what kinds of cloud storage I want to use and how to share what data with others at which access level. As I’m already contemplating on how to use ZFS, I now have two storage concepts to think about.
As a follow up on the Cntlm configuration post last week, here is a small batch file that will find Cntlm.exe (on x86 and x64 systems) then start it in verbose mode.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
I wrote a utility to decode the NTLM blobs that were sent in the IE and HttpWebRequest sessions.When I look at the HttpWebRequest and IE, they both request 56bit and 128bit encryption from the server.
…
In both IE/HttpWebRequest, they are requesting both 64 & 128bit security. However, for windows 7, 128bit security for NTLM has been made the default, and without that, authentication will fail. As you can see from the server response, the server is only supporting 64bit encryption.