As I said, there is stuff that I don't understand in here (including why
browsers apparently do trust alternative chains)
-pd
> On 10 Jun 2020, at 01:53 , Simon Urbanek wrote:
>
> You are making a very strong assumption that finding an alternative chain of
> trust is safe. I'd argue it's
My (also not expert) understanding is that there is nothing insecure about
alternative certificate chains at all. All browsers and macOS's built in
SSL library (secure transport) support them properly. OpenSSL and LibreSSL
were/are simply broken. This was not such a big issue so far, but now that
s
Dear R Developers,
I am having an issue with the renv package and R 4.0.1, which I
suspect is related to base R and not the renv package itself, as with
R 3.6.3 such an "error" does not appear.
The error is raised by a file.exists() path, and path
"C:\Users\J-tel\Documents", which in R 3.6.3 is r
On 10 June 2020 at 13:06, Juan Telleria Ruiz de Aguirre wrote:
| I am having an issue with the renv package and R 4.0.1, which I
| suspect is related to base R and not the renv package itself, as with
| R 3.6.3 such an "error" does not appear.
So a bug in `renv` as it does not account for change
Hi Juan,
For bug reports to R, you should attempt to create a
minimally-reproducible example, using only R's builtin facilities and
not any other addon packages. Given your report, it's not clear
whether the issue lies within renv or truly is caused by a change in R
4.0.0.
Also note that you have
Thank you Kevin, just checked that the error is solved in the latest
development version of "renv", and now it works as expected with R
4.0.1:
https://github.com/rstudio/renv/commit/976ae7af6dc348af30eaf2893d886f132a76aba0
Sorry for posting in r-devel, I was not sure if it was a R or "renv"
error
