stunnel source option (-S) not supported
Bug #345918 reported by
Roman Fiedler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stunnel4 (Debian) |
New
|
Undecided
|
Unassigned | ||
stunnel4 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: stunnel4
The -S (source) option is mentioned in the man pages of stunnel4, but is not available on the command line. The -S option exists in stunnel from the standard stunnel package on hardy, but was removed or renamed in stunnel4.
Tested on hardy
To post a comment you must log in.
It seems that /usr/bin/stunnel is just a compatibility perl-script, that does not know about the -S option, probably because it cannot map it to any option in stunnel4.
Since -S 0 can be used to suppress reading of any other certificate files for validation of remote server/client certs, it would be interesting to know, how the CA-validation process has changed from version 3 to 4.
If the new default is to read only certificates from the specified file/path, then everything is ok.
If new version does include default CA-files, I'm not sure about the consequences. Could it find the default CA-list installed on some machines, so that other clients that use e.g. thawte-signed key/cert to connect while I expected that only client certificates signed by my company's root-CA are accepted? What about latest attacks on md5-signed root CAs?