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

Lorenzo Salvadore phascolarctos at protonmail.ch
Sun Oct 6 15:09:20 UTC 2019


> > > 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 found a solution using --ca-certificate. Please see the patch at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241103

Lorenzo Salvadore.



More information about the svn-ports-all mailing list