Project

General

Profile

Actions
Copy link

Bug #9468

closed

Minicurl fails for https connections

Added by Janos Mattyasovszky over 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System integration
Target version:
4.1.17
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Hi,

When curl is not available, minicurl should handle the transport of the inventory. However, LWP seems to miss the SSL crypto stuff from the build-in modules:

/opt/rudder/bin/rudder-perl /var/rudder/cfengine-community/inputs/common/utilities/minicurl --debug --no-verify --get --file "/var/rudder/cfengine-community/rudder-server-uuid.txt" --url https://rudder.fqdn/uuid
FAILED (501 Protocol scheme 'https' is not supported (Crypt::SSLeay or IO::Socket::SSL not installed))

Since Rudder has changed the default transport to https, this fails on a freshly installed agent out-of-the-box on the first update (given curl is not present).

Found in: rudder-agent-3.1.13.release-1.SLES.12.x86_64

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #6831: Use HTTP for inventory handling on AIX to prevent minicurl errorsReleasedBenoît PECCATTE2015-06-26Actions
Actions
Copy link
 #1

Updated by Matthieu CERDA over 7 years ago

  • Related to Bug #6831: Use HTTP for inventory handling on AIX to prevent minicurl errors added
Actions
Copy link
 #2

Updated by Janos Mattyasovszky over 7 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Benoît PECCATTE about 7 years ago

  • Category set to System integration
  • Target version set to 3.1.19
Actions
Copy link
 #4

Updated by Benoît PECCATTE about 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 34
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
  • Priority changed from 34 to 33
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
  • Priority changed from 33 to 32
Actions
Copy link
 #8

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 32 to 46
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 46 to 45
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 45 to 44
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 44 to 43
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #18

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #21

Updated by François ARMAND over 5 years ago

  • Status changed from New to Rejected
  • Priority changed from 43 to 0

We won't make minicurl https-enable (we tried and failed hardly, and the maintenance cost is prohibitive). We will embed curl+openssl on plateform that currently use minicurl.

I'm closing that ticket, but if you have an use case where minicurl would be better than an embeded curl+openssl, please reopen it!

Actions
Copy link

Also available in: Atom PDF