Posted by jpluimers on 2015/04/10
This is an elaboration of How to fill proxy information in cntlm config file – Stack Overflow.
When digging around how to get authentication stuff going, I want as much information, so this was the command-line I used:
cntlm.exe -v -c cntlm.ini -I -M http://www.bbc.co.uk
The -v is important: it shows you why things fail, and where: It also shows you the NTLM headers sent back/forth over the wire.
These are the switches used:
- -v verbose
- -c configuration file
- -I interactive (prompt for password)
- -M magically detect the NTLM level used by the proxy
Since it is unsafe to store plain text passwords in configuration files, cntlm allows you to store the hashes.
Storing hashes not passwords locally is safer, but not much safer. See for instance Still Passing the Hash 15 Years Later: Guest Post: Let’s talk about Pass-the-Hash by Scriptjunkie the video How to own a Windows Domain or search for Mark Russinovich video windows hash ntlm hack.
Anyway: you can generate the password hashes using either Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, Fiddler, git, HTTP, Internet protocol suite, Mercurial/Hg, NTLM, Power User, Software Development, Source Code Management, TCP, Web Development, Windows, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Vista | Leave a Comment »
Posted by jpluimers on 2015/03/18
Thanks David Millington for pointing me to How to move your Google Code project to GitHub.
A small quote from it:
By the end of this article, you will have:
- Moved the repository, including commit history, from the Google Code project to a new GitHub project
- Updated the Google Code project to redirect to the new project location
- Updated the Google Code repository so users updating will find out they need to use the new project location
- Set up some basic project settings in your new GitHub project.
via: How to move your Google Code project to GitHub.
Posted in Development, DVCS - Distributed Version Control, GitHub, Google, GoogleCode, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2015/03/09
Some links I found useful:
- Git workflows:
- Fork versus clone:
- Git supports multiple remote repositories, of which by convention the default is called `origin` and the one you forked from `upstream`:
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2015/03/03
I am one of the many people complaining about recent SourceTree stability and usability.Issues are not limited to the Windows 1.6.x versions, but since I do most development work on Windows, I wrote Downgrading to SourceTree 1.5.x from 1.6.x, but keeping up with the youngest embedded Git and Mercurial.
This post by Mike Minns (Twitter @brwynant) got my attention: We’re just getting started with SourceTree | SourceTree Blog.
But in order to work with 1.6.x, I’d really love an option to install the 1.6.x versions next to 1.5.x.
- It will take time to trust 1.6.x versions again
- It is a bit cumbersome to do the 1.5.x downgrade
So Mike, if you read is and can make this possible, please get in touch (and if you ever visit the Amsterdam Atlassian office again, lets grab a beer somewhere).
Posted in Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Source Code Management, SourceTree | Leave a Comment »