check if connection was successful on mount

[kradan]

$ ./rs-mount -o debug,...
BEGIN LOG rs-mount Mon Jul 22 19:21:54 2013
[remote] HEAD /
curl_easy_perform() failed with status 60: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt C
RLfile: none
OP GETATTR / (dir)
OP READDIR /
[remote] GET /
curl_easy_perform() failed with status 60: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt C
RLfile: none
READDIR GOT NODE: <Node "/" is_dir=1 size=0 data=0x0>
BEGIN LOG rs-mount Mon Jul 22 19:22:14 2013
BEGIN LOG rs-mount Mon Jul 22 19:22:43 2013
[remote] HEAD /
curl_easy_perform() failed with status 60: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
OP GETATTR / (dir)
OP READDIR /
[remote] GET /
curl_easy_perform() failed with status 60: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
READDIR GOT NODE: <Node "/" is_dir=1 size=0 data=0x0>

[kradan]

It looked, like mounting worked, but ls showed nothing. I added the certificate of the server to my system's CA file and it worked.

This turned out to be useful

DOMAIN=heahdk.net && echo "QUIT"|openssl s_client -connect $DOMAIN:443 | sed -ne "/^-----BEGIN CERTIFICATE/,/^-----END CERTIFICATE/p" > /usr/local/share/ca-certificates/$DOMAIN.crt && update-ca-certificates

[raucao]

Ran into that as well. Tried to mount on Arch after a successful build, but it didn't actually work.