[GRASS-dev] OSGeo Login required to get code

GRASS GRASS developer
1

Hi,

it seems that there is some issue with authentication for Subversion. When I try to download source code using svn checkout I get “Authentication realm: <https://svn.osgeo.org:443> OSGeo Login”. This was observed on two computers with Ubuntu and I can reproduce that in Docker:

docker run -it --rm ubuntu

Using commands:

apt update
apt install subversion
svn checkout [https://svn.osgeo.org/grass/grass/trunk](https://svn.osgeo.org/grass/grass/trunk)

Getting this output (accepting certificate at the beginning and pressing enter at the end):

...
A trunk/lib/raster3d/region.c
A trunk/lib/raster3d/rle.c
A trunk/lib/raster3d/changetype.c
A trunk/lib/raster3d/getblock.c
A trunk/lib/raster3d/test/test_coordinate_transform.c
A trunk/lib/raster3d/error.c
A trunk/lib/raster3d/range.c
A trunk/lib/raster3d/test/test_raster3d_lib.h
Authentication realm: <[https://svn.osgeo.org:443](https://svn.osgeo.org:443)> OSGeo Login
Password for 'root':

Authentication realm: <[https://svn.osgeo.org:443](https://svn.osgeo.org:443)> OSGeo Login
Username:
Password for '':

Authentication realm: <[https://svn.osgeo.org:443](https://svn.osgeo.org:443)> OSGeo Login
Username:
Password for '':

svn: E215004: No more credentials or we tried too many times.
Authentication failed

Expected result is of course checkout without the login prompt which usually comes at the (first) commit.

Is this problem with the client or the server?

Thanks,

Vashek

2

Hi Vaclav,

On Mon, Feb 26, 2018 at 5:16 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

Hi,

it seems that there is some issue with authentication for Subversion. When I
try to download source code using `svn checkout` I get "Authentication
realm: <https://svn.osgeo.org:443> OSGeo Login". This was observed on two
computers with Ubuntu and I can reproduce that in Docker:

docker run -it --rm ubuntu

Using commands:

apt update
apt install subversion
svn checkout https://svn.osgeo.org/grass/grass/trunk

Getting this output (accepting certificate at the beginning and pressing
enter at the end):

```
...
A trunk/lib/raster3d/region.c
A trunk/lib/raster3d/rle.c
A trunk/lib/raster3d/changetype.c
A trunk/lib/raster3d/getblock.c
A trunk/lib/raster3d/test/test_coordinate_transform.c
A trunk/lib/raster3d/error.c
A trunk/lib/raster3d/range.c
A trunk/lib/raster3d/test/test_raster3d_lib.h
Authentication realm: <https://svn.osgeo.org:443> OSGeo Login
Password for 'root':

Why should it request that at all? You can anonymously checkout the
code, can't you?

I just updated all my OSGeo SVN repos I am following, no problem at all.

Another test, on Fedora 27:

[mneteler@oboe ~ ]$ mkdir bla
[mneteler@oboe ~ ]$ cd bla
[mneteler@oboe bla ]$ svn co https://svn.osgeo.org/grass/grass-promo
A grass-promo/grasslogo
A grass-promo/screenshots
A grass-promo/screenshots/wxpython
A grass-promo/screenshots/wxpython/location_wizard
A grass-promo/screenshots/wxpython/general
A grass-promo/screenshots/wxpython/digitization
A grass-promo/grassflyer
A grass-promo/grassflyer/flyer1
A grass-promo/grassflyer/flyer1/es
A grass-promo/grasslogo/ascii_logo_bold.svg
A grass-promo/screenshots/wxpython/digitization/digit-gism.png
...

It does not ask me to accept the certificate nor should it (IMHO)!
Maybe some local issue at your end with the certificate introducing
other troubles?
Or, it was a temporary problem?

Markus

3

On Mon, Feb 26, 2018 at 1:33 AM, Markus Neteler <neteler@osgeo.org> wrote:

On Mon, Feb 26, 2018 at 5:16 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

it seems that there is some issue with authentication for Subversion. When I
try to download source code using svn checkout I get “Authentication
realm: <https://svn.osgeo.org:443> OSGeo Login”. This was observed on two
computers with Ubuntu and I can reproduce that in Docker:

docker run -it --rm ubuntu

…
A trunk/lib/raster3d/test/test_raster3d_lib.h
Authentication realm: <https://svn.osgeo.org:443> OSGeo Login
Password for ‘root’:

Why should it request that at all? You can anonymously checkout the
code, can’t you?

You should be able, but that’s what I can’t do.

I just updated all my OSGeo SVN repos I am following, no problem at all.

Do you mean on your computer where you entered credentials in past to get write access? That would be the difference. The two computers I mentioned were a fresh install without someone’s credentials as well as the Docker test.

Another test, on Fedora 27:

[mneteler@oboe ~ ]$ mkdir bla
[mneteler@oboe ~ ]$ cd bla
[mneteler@oboe bla ]$ svn co https://svn.osgeo.org/grass/grass-promo
A grass-promo/grasslogo
A grass-promo/screenshots
A grass-promo/screenshots/wxpython
A grass-promo/screenshots/wxpython/location_wizard
A grass-promo/screenshots/wxpython/general
A grass-promo/screenshots/wxpython/digitization
A grass-promo/grassflyer
A grass-promo/grassflyer/flyer1
A grass-promo/grassflyer/flyer1/es
A grass-promo/grasslogo/ascii_logo_bold.svg
A grass-promo/screenshots/wxpython/digitization/digit-gism.png
…

It does not ask me to accept the certificate nor should it (IMHO)!

It says “The certificate is not issued by a trusted authority”. After accepting permanently, it does not ask again as expected.

Maybe some local issue at your end with the certificate introducing
other troubles?

No idea, seems independent, but appeared at a similar time (the certificate issue may not happen outside of Docker, not sure).

Or, it was a temporary problem?

I can’t try the other computers now, but in Docker, I still get the same result:

docker run -it --rm ubuntu

apt update -y
apt install -y subversion
svn checkout https://svn.osgeo.org/grass/grass/trunk

Error validating server certificate for ‘https://svn.osgeo.org:443’:

  • The certificate is not issued by a trusted authority. Use the
    fingerprint to validate the certificate manually!
    Certificate information:
  • Hostname: *.osgeo.org
  • Valid: from Apr 28 00:00:00 2016 GMT until May 1 23:59:59 2019 GMT
  • Issuer: SSL.com DV CA, www.ssl.com, SSL.com, US
  • Fingerprint: 56:50:0D:63:0F:47:10:92:7A:3A:B5:A9:83:F8:97:92:FE:D6:19:95
    (R)eject, accept (t)emporarily or accept (p)ermanently?
    …
    A trunk/misc/m.measure/main.c
    A trunk/misc/m.cogo/TODO
    A trunk/misc/m.cogo/Makefile
    A trunk/testsuite/vector/v.in.gps_test.sh
    A trunk/testsuite/Makefile
    A trunk/testsuite/README
    …
    Authentication realm: <https://svn.osgeo.org:443> OSGeo Login
    Password for ‘root’:
4

Right!

The

…

Could it be that the pool of certificate authorities is outdated in your docker?
Is it up to date?

···

Am 26.02.2018 3:42 nachm. schrieb “Vaclav Petras” <wenzeslaus@gmail.com>:

…

Do you mean on your computer where you entered credentials in past to get write access? That would be the difference.

two computers I mentioned were a fresh install without someone’s credentials as well as the Docker test.

No idea, seems independent, but appeared at a similar time (the certificate issue may not happen outside of Docker, not sure).

Or, it was a temporary problem?

I can’t try the other computers now, but in Docker, I still get the same result:

docker run -it --rm ubuntu

apt update -y
apt install -y subversion
svn checkout https://svn.osgeo.org/grass/grass/trunk

Error validating server certificate for ‘https://svn.osgeo.org:443’:

  • The certificate is not issued by a trusted authority. Use the
    fingerprint to validate the certificate manually!
    Certificate information:
  • Hostname: *.osgeo.org
  • Valid: from Apr 28 00:00:00 2016 GMT until May 1 23:59:59 2019 GMT
  • Issuer: SSL.com DV CA, www.ssl.com, SSL.com, US
  • Fingerprint: 56:50:0D:63:0F:47:10:92:7A:3A:B5:A9:83:F8:97:92:FE:D6:19:95
    (R)eject, accept (t)emporarily or accept (p)ermanently?

…
A trunk/misc/m.measure/main.c
A trunk/misc/m.cogo/TODO
A trunk/misc/m.cogo/Makefile
A trunk/testsuite/vector/v.in.gps_test.sh
A trunk/testsuite/Makefile
A trunk/testsuite/README
…

Authentication realm: <https://svn.osgeo.org:443> OSGeo Login
Password for ‘root’:

I’m traveling so I cannot easily check now… maybe someone else could try with a docker generated from a different distro?

Markus

5

On Mon, Feb 26, 2018 at 9:49 AM, Markus Neteler <neteler@osgeo.org> wrote:

Am 26.02.2018 3:42 nachm. schrieb “Vaclav Petras” <wenzeslaus@gmail.com>:

…

Error validating server certificate for ‘https://svn.osgeo.org:443’:

  • The certificate is not issued by a trusted authority. Use the
    fingerprint to validate the certificate manually!
    Certificate information:
  • Hostname: *.osgeo.org
  • Valid: from Apr 28 00:00:00 2016 GMT until May 1 23:59:59 2019 GMT
  • Issuer: SSL.com DV CA, www.ssl.com, SSL.com, US
  • Fingerprint: 56:50:0D:63:0F:47:10:92:7A:3A:B5:A9:83:F8:97:92:FE:D6:19:95
    (R)eject, accept (t)emporarily or accept (p)ermanently?

Could it be that the pool of certificate authorities is outdated in your docker?
Is it up to date?

Installing the ca-certificates removes the certificate waring/prompt. Still the svn checkout ask for credentials.

docker run -it --rm ubuntu

apt update -y
apt install -y subversion ca-certificates
svn checkout [https://svn.osgeo.org/grass/grass/trunk](https://svn.osgeo.org/grass/grass/trunk)

I’m traveling so I cannot easily check now… maybe someone else could try with a docker generated from a different distro?

Same on Fedora in Docker (except the certificate):

docker run -it --rm fedora bash

yum update -y
yum install -y subversion
svn checkout [https://svn.osgeo.org/grass/grass/trunk](https://svn.osgeo.org/grass/grass/trunk)

...
Authentication realm: <[https://svn.osgeo.org:443](https://svn.osgeo.org:443)> OSGeo Login
Password for 'root':

In all cases, it happens after a random number of downloaded files, not at the beginning or after a specific file.

6

…

···

Am 26.02.2018 5:35 nachm. schrieb “Vaclav Petras” <wenzeslaus@gmail.com>:

svn checkout https://svn.osgeo.org/grass/grass/trunk

…
Authentication realm: <https://svn.osgeo.org:443> OSGeo Login
Password for ‘root’:


In all cases, it happens after a random number of downloaded files, not at the beginning or after a specific file.

In this case is suggest to open a SAC ticket. Several servers get updated at time, perhaps there was a recent update I’m not aware of.

Markus

7

On Mon, Feb 26, 2018 at 5:40 PM, Markus Neteler <neteler@osgeo.org> wrote:

In this case is suggest to open a SAC ticket. Several servers get updated
at time, perhaps there was a recent update I'm not aware of.

I forgot to say I did that. It was accepted as blocker.

https://trac.osgeo.org/osgeo/ticket/2128