Old CentOS 5.6, Due to github.com delete the TLSv1/TLSv1.1 support, How can I access to github.com/repo.git using git system
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Now I have a cluster with Rocks 5.4 based on CentOS 5.6. When I git push the code to github.com, I run into the errors:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing http://github.com/
related link:
Compile Git to use OpenSSL library libssl.so.1.0.1
https://githubengineering.com/crypto-removal-notice/
Hope someone give a solution. Thank you very much!
Qiang
linux centos git openssl github
edited May 19 at 9:39
Thomas
3,38741023
asked May 18 at 22:46
Qiang L
11
add a comment |Â
up vote
0
down vote
favorite
Now I have a cluster with Rocks 5.4 based on CentOS 5.6. When I git push the code to github.com, I run into the errors:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing http://github.com/
related link:
Compile Git to use OpenSSL library libssl.so.1.0.1
https://githubengineering.com/crypto-removal-notice/
Hope someone give a solution. Thank you very much!
Qiang
linux centos git openssl github
edited May 19 at 9:39
Thomas
3,38741023
asked May 18 at 22:46
Qiang L
11
2
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
1
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Now I have a cluster with Rocks 5.4 based on CentOS 5.6. When I git push the code to github.com, I run into the errors:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing http://github.com/
related link:
Compile Git to use OpenSSL library libssl.so.1.0.1
https://githubengineering.com/crypto-removal-notice/
Hope someone give a solution. Thank you very much!
Qiang
linux centos git openssl github
edited May 19 at 9:39
Thomas
3,38741023
asked May 18 at 22:46
Qiang L
11
Now I have a cluster with Rocks 5.4 based on CentOS 5.6. When I git push the code to github.com, I run into the errors:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing http://github.com/
related link:
Compile Git to use OpenSSL library libssl.so.1.0.1
https://githubengineering.com/crypto-removal-notice/
Hope someone give a solution. Thank you very much!
Qiang
linux centos git openssl github
edited May 19 at 9:39
Thomas
3,38741023
asked May 18 at 22:46
Qiang L
11
edited May 19 at 9:39
Thomas
3,38741023
edited May 19 at 9:39
Thomas
3,38741023
edited May 19 at 9:39
Thomas
3,38741023
3,38741023
asked May 18 at 22:46
Qiang L
11
asked May 18 at 22:46
Qiang L
11
asked May 18 at 22:46
Qiang L
11
11
2
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
1
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28
add a comment |Â
2
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
1
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28
2
2
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
1
1
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
There are a lot of people still running RHEL 5 / CentOS 5 for several reasons. Unfortunately RHEL 5 is out of support and additionally there was never a package with OpenSSL >= 1 for RHEL 5.
If you don't have any concerns about using a foreign repo then you can use "tuxad repo". It provides a different and more easy way to update OpenSSL of RHEL 5 to the one of RHEL 6 (which is still supported):
- Install tuxad repo for RHEL 5: rpm -i http://www.tuxad.de/repo/5/tuxad.rpm
- Update packages: yum update
More details can be found here:
www.tuxad.de/blog/archives/2014/11/19/openssl_updatesenhancements_for_rhel__centos_5
www.tuxad.de/blog/archives/2018/07/21/tuxad_rh5_repo_now_with_phpopenssl1
This repo contains several packages which are rebuild against OpenSSL 1:
- httpd (also include other enhancements like ECDH support)
- postfix
- dovecot
- curl
- lynx
- mutt
- vsftpd
- w3m
- wget
- php
- php from RHEL 6 backported (in separate repo "tuxad-php")
answered Jul 29 at 15:19
reichhart
1464
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
There are a lot of people still running RHEL 5 / CentOS 5 for several reasons. Unfortunately RHEL 5 is out of support and additionally there was never a package with OpenSSL >= 1 for RHEL 5.
If you don't have any concerns about using a foreign repo then you can use "tuxad repo". It provides a different and more easy way to update OpenSSL of RHEL 5 to the one of RHEL 6 (which is still supported):
- Install tuxad repo for RHEL 5: rpm -i http://www.tuxad.de/repo/5/tuxad.rpm
- Update packages: yum update
More details can be found here:
www.tuxad.de/blog/archives/2014/11/19/openssl_updatesenhancements_for_rhel__centos_5
www.tuxad.de/blog/archives/2018/07/21/tuxad_rh5_repo_now_with_phpopenssl1
This repo contains several packages which are rebuild against OpenSSL 1:
- httpd (also include other enhancements like ECDH support)
- postfix
- dovecot
- curl
- lynx
- mutt
- vsftpd
- w3m
- wget
- php
- php from RHEL 6 backported (in separate repo "tuxad-php")
answered Jul 29 at 15:19
reichhart
1464
add a comment |Â
up vote
0
down vote
There are a lot of people still running RHEL 5 / CentOS 5 for several reasons. Unfortunately RHEL 5 is out of support and additionally there was never a package with OpenSSL >= 1 for RHEL 5.
If you don't have any concerns about using a foreign repo then you can use "tuxad repo". It provides a different and more easy way to update OpenSSL of RHEL 5 to the one of RHEL 6 (which is still supported):
- Install tuxad repo for RHEL 5: rpm -i http://www.tuxad.de/repo/5/tuxad.rpm
- Update packages: yum update
More details can be found here:
www.tuxad.de/blog/archives/2014/11/19/openssl_updatesenhancements_for_rhel__centos_5
www.tuxad.de/blog/archives/2018/07/21/tuxad_rh5_repo_now_with_phpopenssl1
This repo contains several packages which are rebuild against OpenSSL 1:
- httpd (also include other enhancements like ECDH support)
- postfix
- dovecot
- curl
- lynx
- mutt
- vsftpd
- w3m
- wget
- php
- php from RHEL 6 backported (in separate repo "tuxad-php")
answered Jul 29 at 15:19
reichhart
1464
add a comment |Â
up vote
0
down vote
up vote
0
down vote
There are a lot of people still running RHEL 5 / CentOS 5 for several reasons. Unfortunately RHEL 5 is out of support and additionally there was never a package with OpenSSL >= 1 for RHEL 5.
If you don't have any concerns about using a foreign repo then you can use "tuxad repo". It provides a different and more easy way to update OpenSSL of RHEL 5 to the one of RHEL 6 (which is still supported):
- Install tuxad repo for RHEL 5: rpm -i http://www.tuxad.de/repo/5/tuxad.rpm
- Update packages: yum update
More details can be found here:
www.tuxad.de/blog/archives/2014/11/19/openssl_updatesenhancements_for_rhel__centos_5
www.tuxad.de/blog/archives/2018/07/21/tuxad_rh5_repo_now_with_phpopenssl1
This repo contains several packages which are rebuild against OpenSSL 1:
- httpd (also include other enhancements like ECDH support)
- postfix
- dovecot
- curl
- lynx
- mutt
- vsftpd
- w3m
- wget
- php
- php from RHEL 6 backported (in separate repo "tuxad-php")
answered Jul 29 at 15:19
reichhart
1464
There are a lot of people still running RHEL 5 / CentOS 5 for several reasons. Unfortunately RHEL 5 is out of support and additionally there was never a package with OpenSSL >= 1 for RHEL 5.
If you don't have any concerns about using a foreign repo then you can use "tuxad repo". It provides a different and more easy way to update OpenSSL of RHEL 5 to the one of RHEL 6 (which is still supported):
- Install tuxad repo for RHEL 5: rpm -i http://www.tuxad.de/repo/5/tuxad.rpm
- Update packages: yum update
More details can be found here:
www.tuxad.de/blog/archives/2014/11/19/openssl_updatesenhancements_for_rhel__centos_5
www.tuxad.de/blog/archives/2018/07/21/tuxad_rh5_repo_now_with_phpopenssl1
This repo contains several packages which are rebuild against OpenSSL 1:
- httpd (also include other enhancements like ECDH support)
- postfix
- dovecot
- curl
- lynx
- mutt
- vsftpd
- w3m
- wget
- php
- php from RHEL 6 backported (in separate repo "tuxad-php")
answered Jul 29 at 15:19
reichhart
1464
answered Jul 29 at 15:19
reichhart
1464
answered Jul 29 at 15:19
reichhart
1464
answered Jul 29 at 15:19
reichhart
1464
1464
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444720%2fold-centos-5-6-due-to-github-com-delete-the-tlsv1-tlsv1-1-support-how-can-i-ac%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
Two options, either upgrading to a more recent CentOS, or setting up a frontend service/Server that talks a more recent version of TLS.
– Rui F Ribeiro
May 18 at 22:47
1
CentOS 5 is well past its end of life; I would think long and hard about whether you want to continue using unsupported infrastructure as opposed to running something current wherein you will not be encountering this sort of issue.
– DopeGhoti
May 18 at 22:50
Because It is the old cluster, upgrading more recent CentOS may bring more pains, So that is not my options. About another solution may give some details?
– Qiang L
May 18 at 22:50
CentOS 5 is dead. You are only going to continue to encounter situations like this, rendering your cluster useless. Spend your energy building a new cluster with a supported OS.
– jsbillings
May 22 at 23:28