Q: howto require per-branch authentication to commit or push changes
Michael B. Trausch
mike at trausch.us
Sat Apr 4 06:11:35 BST 2009
On Fri, 3 Apr 2009 18:08:06 -0700
Maritza Mendez <martitzam at gmail.com> wrote:
> On Fri, Apr 3, 2009 at 5:20 PM, Michael B. Trausch <mike at trausch.us>
> > You should be able to use group permissions to handle the problem on
> > the remote host.
> That is a very good suggestion. I was wanting to avoid figuring out
> how to run ssh on Windows, but I think you are right this is the best
> way. Our IT guy does not want any non-Windows boxes. Aye! It was
> hard enough to get bzr to run as a Windows Service! This would be so
> much easier if he would let us use Linux. I think there is a saying
> those who do not know unix are doomed to reinvent poor substitutes.
Are you serious? I'm going to have to agree with Ben's response---you
need to get a new IT guy (or at least convince him of his stupidity) or
get him to leave. I have a client that has an IT guy like that; the
client pays the IT guy to manage the client machines on the network and
I handle the server stuff because their IT guy can't handle anything
but Windows Server and a mouse. *shrug*
That said, if you are stuck running on Windows, see if there is a way
that you can adapt it to fit. Windows has the concepts of users and
groups down, though I don't know if you can (as quickly) set up
something that runs like bzr over ssh does. You may be able to get
something going with Cygwin, but I'd rather use a real Linux box
instead of Cygwin for performance and security reasons.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090404/9117aaac/attachment.pgp
More information about the bazaar