svn commit: r513655 - in head/security: . protonvpn-cli protonvpn-cli/files

[Lorenzo Salvadore]

Hello. As I was not subscribed to this list I was contacted privately to reply
to this:

>>   New port: security/protonvpn-cli
>> +PLIST_FILES=	bin/protonvpn-cli \
>> +		bin/pvpn \
>> +		etc/openvpn/update-resolv-conf
>> +
>> +post-patch:
>> +	${REINPLACE_CMD} s,\$$python,${PYTHON_CMD},g ${WRKSRC}/protonvpn-cli.sh
>> +	${REINPLACE_CMD} s,wget,wget\ --no-check-certificate,g ${WRKSRC}/protonvpn-cli.sh
>
>This at least sounds like a bad idea, and would at the very least need a comment
>of explanation

I agree that --no-check-certificate sounds like a bad idea, however I was unable to get the port working
without it. According to my researches on the web installing ca_root_nss should have fixed the problem
but it did not: maybe I should have specified some argument so that wget actually uses ca_root_nss?

If someone can suggest a better solution that --no-check-certificate, I would be glad to try it. I will also try
to found one myself.

I am now subscribed to this mailing list so there will be no need to contact me separately any more.

Thank you.

Lorenzo Salvadore.

Sent with [ProtonMail](https://protonmail.com) Secure Email.