Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-12-01 Thread JITHIN K
Hi Arun,

My objective was to move SVN repos to a new platform so I used svnsync
command to create a mirror of SVN repos in the new server.

 I used svnsync over http and restrict access limited to source and
destination server. I enabled SVN over HTTPS after the successful execution
the svnsync.

Regards,
Jithin K
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread JITHIN K
On Mon, Nov 30, 2015 at 9:45 PM, Shakthi Kannan 
wrote:

> Hi,
>
> --- On Mon, Nov 30, 2015 at 9:39 PM, JITHIN K  wrote:
> | Output "svn: OPTIONS of 'https://192.168.0.1.1/svn/AJ': SSL handshake
> | failed: SSL error: A TLS warning alert has been received. (
> | https://192.168.1.1)"
> \--
>
> How were the SSL certificates generated?
>
> Try these (for a start):
>
>
> http://stackoverflow.com/questions/16805298/svn-and-ssl-handshake-failure
>
>
> http://e-mats.org/2012/11/svn-options-of-ssl-handshake-failed-ssl-error-a-tls-warning-alert-has-been-received/
>
>
> http://www.kpsolution.com/linux/svn-ssl-handshake-failed-ssl-error-a-tls-warning-alert-has-been-received/146/
>
> SK
>
> --
> Shakthi Kannan
> http://www.shakthimaan.com
> ___
> ILUGC Mailing List:
> http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
> ILUGC Mailing List Guidelines:
> http://ilugc.in/mailinglist-guidelines
>


Hi Shakthi,

Appreciate your response.

I used the following command to generate the certificate.

sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout
/etc/ssl/apache2.key -out /etc/ssl/apache2.crt


FYI,

I just checked in Ubuntu 12.04 and Ubuntu 14.04.

I only face issues with *Ubuntu 10.04 and Ubuntu 9.10. *

Regards,
Jithin k
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread Shakthi Kannan
Hi,

--- On Mon, Nov 30, 2015 at 10:14 PM, JITHIN K  wrote:
| I only face issues with *Ubuntu 10.04 and Ubuntu 9.10. *
\--

Are these Ubuntu distributions LTS?

Please trim your posts when you reply. Only keep the text that is
relevant. We follow trimmed, interleaved, bottom posting.

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread L. Guruprasad
Hi Jithin,

On 11/30/15 10:28 PM, JITHIN K wrote:
> Hi Shakthi,
> 
> Ubuntu 9.10 is not LTS (Ubuntu 10.04 is LTS). Its an old unsupportable
> version.

I'm just guessing here but since these distributions are very old, these
errors could be due to the usage of unsupported protocols/ciphers.


That said, these are unsupported releases and even Ubuntu 10.04 LTS
reached EOL some time earlier this year. So you shouldn't be using it.

Thanks & Regards,
Guruprasad





signature.asc
Description: OpenPGP digital signature
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines

[Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread JITHIN K
Hi All,

I tried to run the svn list of a remote SVN server (Which is newly
installed ) but it failed with the following error.

Command : sudo svn info https://192.168.1.1/svn/AJ

Output "svn: OPTIONS of 'https://192.168.0.1.1/svn/AJ': SSL handshake
failed: SSL error: A TLS warning alert has been received. (
https://192.168.1.1)"


Server OS : Ubuntu 12.04.5
SVN version : 1.6.17
Clients : Ubuntu 12.04,Ubuntu 10.04

*But it worked on Windows Clients (Command mode), TortoiseSVN etc*


Options tried.

1. --trust-server-cert [Along with non-interactive] - Failed.

Any suggestions / idea is appreciable.


Regards,
Jithin K
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread Shakthi Kannan
Hi,

--- On Mon, Nov 30, 2015 at 9:39 PM, JITHIN K  wrote:
| Output "svn: OPTIONS of 'https://192.168.0.1.1/svn/AJ': SSL handshake
| failed: SSL error: A TLS warning alert has been received. (
| https://192.168.1.1)"
\--

How were the SSL certificates generated?

Try these (for a start):

  http://stackoverflow.com/questions/16805298/svn-and-ssl-handshake-failure

  
http://e-mats.org/2012/11/svn-options-of-ssl-handshake-failed-ssl-error-a-tls-warning-alert-has-been-received/

  
http://www.kpsolution.com/linux/svn-ssl-handshake-failed-ssl-error-a-tls-warning-alert-has-been-received/146/

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread JITHIN K
Hi Guruprasad,

Thanks for the response.

The objective is to move all the SVN repositories from Ubuntu 9.10,Ubuntu
10.04 to Ubuntu 12.04. I am using svnsync command to keep a mirror copy of
the repository in the new server and once the syn over. I will decommission
the Ubuntu 9.10 and Ubuntu 10.04.  I know that I could use svn dump for
moving the repositories but I think svnsync is more suitable for my
environment.

I just found a work around for this solution by syncing over HTTP.

Thank you

Regards,
Jithin K
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines


Re: [Ilugc] SSL handshake failed: SSL error: A TLS warning alert has been received

2015-11-30 Thread Arun Khan
On Mon, Nov 30, 2015 at 11:37 PM, JITHIN K  wrote:
>
> I just found a work around for this solution by syncing over HTTP.
>

Please share your workaround so that others with a similar use case
scenario can benefit from your knowledge.

+1 about upgrading your OS to a supported version.  I have seen cases
of Fedora 4 still running on public facing interfaces!

Most security incidents are caused because of lack of system upgrades
(OS + application stack).

-- Arun Khan
___
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
ILUGC Mailing List Guidelines:
http://ilugc.in/mailinglist-guidelines