On Fri, Dec 4, 2015 at 11:25 AM, Mark Phippard <markp...@gmail.com> wrote:
> On Fri, Dec 4, 2015 at 11:19 AM, foven <effo...@gmail.com> wrote: > >> On Thu, Dec 3, 2015 at 8:20 PM, Mark Phippard <markp...@gmail.com> wrote: >> >>> What I was thinking is that the hook they've installed would have >>> something in it to work in the ssh environment they've configured and be >>> able to call your hook as their docs describe. >>> >>> > >> That would make sense, but unfortunately when their script (or any >>> >> other) is installed, commits just cause the exit code 255 error, >> regardless of any custom hooks I create. >> >> Any other thoughts? >> >> > > Your issues seem more specific to Phabricator and how they setup their > environment. I would try their IRC channel or see if they have any forums > or a public issue tracker you could post in. Their software looks like it > would want to manage the environment so it would be best to pursue a > solution that they provide. > > -- > Thanks > > Mark Phippard > http://markphip.blogspot.com/ > I actually started trying to solve this in their IRC channel, but eventually it was suggested that it might be something specific to svn. After your reply I spoke with some people via Phabricator's web chat interface and at their suggestion I will be opening a task for this issue. I'm still not sure if this is a Phabricator issue or a Subversion one, or some combination of the two, but hopefully between this mailing list and the developers from the Phabricator team, a solution will be found soon. Speaking of the mailing list, I noticed on http://svn.haxx.se/users/ that there were recently some replies in this thread that I seem not to have received. I'm not sure if there is a better way for me to reply to these or not, so I will do so here. From: Thorsten Schöning <tschoening_at_am-soft.de> Date: Fri, 4 Dec 2015 23:34:38 +0100 Guten Tag foven, am Donnerstag, 3. Dezember 2015 um 21:55 schrieben Sie: > AuthorizedKeysCommand /usr/libexec/phabricator-ssh-hook.sh > AuthorizedKeysCommandUser vcs Did you have a look at that script, is it maybe doing more than just authorization? Does it handle svn+ssh different from if you ssh and execute svn commits using file:///? Mit freundlichen Grüßen, Thorsten Schöning I will look into this, but I'm fairly sure that authorization is all it does. The documentation for sshd_config states that this property "specifies a program to be used to look up the user's public keys". It "should produce on standard output zero or more lines of authorized_keys output". So far as a difference between svn+ssh and ssh followed by svn commits using file:///, I'm pretty sure the way that instance of sshd is configured, it isn't possible to simply ssh in and then run commands. I'm not able to access the server at the moment, but I don't think it is possible. There is another sshd instance running however, with a more typical configuration and that is the one where I was able to ssh, then svn commit file:///. From: Nico Kadel-Garcia <nkadel_at_gmail.com> Date: Fri, 4 Dec 2015 23:09:45 -0500 Is SELinux enabled? Received on 2015-12-05 05:09:51 CET No, SELinux is disabled.
