SSL and programs like wget,curl with https on hpux
up vote
0
down vote
favorite
Simple question: every program (wget,curl,etc) which can use https works perfect on linux,and bad on hpux.
See this example using https://google.com
on linux
wget https://www.google.com/
--2018-12-04 16:47:27-- https://www.google.com/
Resolving www.google.com... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com|64.233.166.99|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'
index.html [ <=> ] 11.78K --.-KB/s in 0.01s
2018-12-04 16:47:27 (949 KB/s) - 'index.html' saved [12063]
and I get the file
on hp-ux
wget https://www.google.com/
--2018-12-04 16:48:46-- https://www.google.com/
Resolving www.google.com (www.google.com)... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com (www.google.com)|64.233.166.99|:443... connected.
ERROR: The certificate of 'www.google.com' is not trusted.
ERROR: The certificate of 'www.google.com' doesn't have a known issuer.
ERROR: The certificate of 'www.google.com' was signed using an insecure algorithm.
and I get..nothing.
I run the command
c_rehash
and
/usr/local/bin/c_reash
But nothing change.
openssl hp-ux
asked Dec 4 at 15:50
elbarna
4,047103679
add a comment |
up vote
0
down vote
favorite
Simple question: every program (wget,curl,etc) which can use https works perfect on linux,and bad on hpux.
See this example using https://google.com
on linux
wget https://www.google.com/
--2018-12-04 16:47:27-- https://www.google.com/
Resolving www.google.com... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com|64.233.166.99|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'
index.html [ <=> ] 11.78K --.-KB/s in 0.01s
2018-12-04 16:47:27 (949 KB/s) - 'index.html' saved [12063]
and I get the file
on hp-ux
wget https://www.google.com/
--2018-12-04 16:48:46-- https://www.google.com/
Resolving www.google.com (www.google.com)... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com (www.google.com)|64.233.166.99|:443... connected.
ERROR: The certificate of 'www.google.com' is not trusted.
ERROR: The certificate of 'www.google.com' doesn't have a known issuer.
ERROR: The certificate of 'www.google.com' was signed using an insecure algorithm.
and I get..nothing.
I run the command
c_rehash
and
/usr/local/bin/c_reash
But nothing change.
openssl hp-ux
asked Dec 4 at 15:50
elbarna
4,047103679
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Simple question: every program (wget,curl,etc) which can use https works perfect on linux,and bad on hpux.
See this example using https://google.com
on linux
wget https://www.google.com/
--2018-12-04 16:47:27-- https://www.google.com/
Resolving www.google.com... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com|64.233.166.99|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'
index.html [ <=> ] 11.78K --.-KB/s in 0.01s
2018-12-04 16:47:27 (949 KB/s) - 'index.html' saved [12063]
and I get the file
on hp-ux
wget https://www.google.com/
--2018-12-04 16:48:46-- https://www.google.com/
Resolving www.google.com (www.google.com)... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com (www.google.com)|64.233.166.99|:443... connected.
ERROR: The certificate of 'www.google.com' is not trusted.
ERROR: The certificate of 'www.google.com' doesn't have a known issuer.
ERROR: The certificate of 'www.google.com' was signed using an insecure algorithm.
and I get..nothing.
I run the command
c_rehash
and
/usr/local/bin/c_reash
But nothing change.
openssl hp-ux
asked Dec 4 at 15:50
elbarna
4,047103679
Simple question: every program (wget,curl,etc) which can use https works perfect on linux,and bad on hpux.
See this example using https://google.com
on linux
wget https://www.google.com/
--2018-12-04 16:47:27-- https://www.google.com/
Resolving www.google.com... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com|64.233.166.99|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'
index.html [ <=> ] 11.78K --.-KB/s in 0.01s
2018-12-04 16:47:27 (949 KB/s) - 'index.html' saved [12063]
and I get the file
on hp-ux
wget https://www.google.com/
--2018-12-04 16:48:46-- https://www.google.com/
Resolving www.google.com (www.google.com)... 64.233.166.99, 64.233.166.106, 64.233.166.105, ...
Connecting to www.google.com (www.google.com)|64.233.166.99|:443... connected.
ERROR: The certificate of 'www.google.com' is not trusted.
ERROR: The certificate of 'www.google.com' doesn't have a known issuer.
ERROR: The certificate of 'www.google.com' was signed using an insecure algorithm.
and I get..nothing.
I run the command
c_rehash
and
/usr/local/bin/c_reash
But nothing change.
openssl hp-ux
openssl hp-ux
asked Dec 4 at 15:50
elbarna
4,047103679
asked Dec 4 at 15:50
elbarna
4,047103679
asked Dec 4 at 15:50
elbarna
4,047103679
asked Dec 4 at 15:50
elbarna
4,047103679
asked Dec 4 at 15:50
elbarna
4,047103679
4,047103679
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485935%2fssl-and-programs-like-wget-curl-with-https-on-hpux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485935%2fssl-and-programs-like-wget-curl-with-https-on-hpux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
