You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Felix Röthenbacher (JIRA)" <ji...@codehaus.org> on 2009/03/17 03:21:12 UTC

[jira] Created: (CONTINUUM-2133) svn: PROPFIND request failed. Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted

svn: PROPFIND request failed. Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted
----------------------------------------------------------------------------------------------------------------------------------------

                 Key: CONTINUUM-2133
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2133
             Project: Continuum
          Issue Type: Bug
          Components: SCM
    Affects Versions: 1.2.3
         Environment: Linux
            Reporter: Felix Röthenbacher


Updating from a Subversion repository using https with a SSL certificate which needs to be accepted first fails when run under a different user (run-as-user).

The shell start script for Continuum has an option to run Continuum as a different user. The problem is that su preserves the current environment not
setting the HOME environment variable to the run-as user's home. Hence svn does not pickup any permanently accepted SSL certificates under the users
$HOME/.subversion/auth/svn.ssl.server/ directory.

Workaround is to specify the HOME directory of the user running Continuum in the startup script.

Alternatively, the su command could use a direct login shell instead of preserving the current environment but not sure if there are any
security issues to consider.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Updated: (CONTINUUM-2133) ability to register Subversion server SSL certificates from within continuum

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-2133:
------------------------------------

    Fix Version/s: 1.x
       Issue Type: New Feature  (was: Bug)
          Summary: ability to register Subversion server SSL certificates from within continuum  (was: svn: PROPFIND request failed. Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted)

changed this to a more appropriate feature request since there is already a decent workaround in the comments

> ability to register Subversion server SSL certificates from within continuum
> ----------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2133
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2133
>             Project: Continuum
>          Issue Type: New Feature
>          Components: SCM
>    Affects Versions: 1.2.3
>         Environment: Linux
>            Reporter: Felix Röthenbacher
>             Fix For: 1.x
>
>
> Updating from a Subversion repository using https with a SSL certificate which needs to be accepted first fails when run under a different user (run-as-user).
> The shell start script for Continuum has an option to run Continuum as a different user. The problem is that su preserves the current environment not
> setting the HOME environment variable to the run-as user's home. Hence svn does not pickup any permanently accepted SSL certificates under the users
> $HOME/.subversion/auth/svn.ssl.server/ directory.
> Workaround is to specify the HOME directory of the user running Continuum in the startup script.
> Alternatively, the su command could use a direct login shell instead of preserving the current environment but not sure if there are any
> security issues to consider.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira