On 10/06/2020 00:39, peter dalgaard wrote:
Yes and no... At least as I understand it (Disclaimer: There are things I am
pretty sure that I don't understand properly, somewhere in the Bermuda triangle
beween CA bundles, TLS protocols, and Server-side settings), there are two
sided to this:
One
It is known, with a known workaround, see e.g.
https://www.stats.ox.ac.uk/pub/bdr/memtests/README.txt . Set
suppressions in ~/.valgrindrc, e.g. the CRAN check machine has
--suppressions=/data/blackswan/ripley/wcsrtombs.supp
It is an issue in your OS (glibc), not TRE nor R.
On 10/06/2020 00:2
You are making a very strong assumption that finding an alternative chain of
trust is safe. I'd argue it's not - it means that an adversary could manipulate
the chain in a way to trust it instead of the declared chain and thus
subverting it. In fact switching to OpenSSL would create a serious se
Yes and no... At least as I understand it (Disclaimer: There are things I am
pretty sure that I don't understand properly, somewhere in the Bermuda triangle
beween CA bundles, TLS protocols, and Server-side settings), there are two
sided to this:
One is that various *.r-project.org servers got
Hi all,
I'm on Ubuntu 18.04, running R-4.0.0 which I compiled from source, and
using valgrind I am always seeing the following message. Does anybody
else see that? Is that a known false positive? Any ideas how to
fix/suppress? Seems related to TRE, do I need to upgrade that?
(base) tdhock@maude-M
To be clear, this not an issue in the libraries nor R, the certificates on the
server were simply wrong. So, no, this has nothing to do with R.
Cheers,
Simon
> On Jun 10, 2020, at 10:45 AM, Henrik Bengtsson
> wrote:
>
> Was this resolved upstream or is this something that R should/could
> fi
Was this resolved upstream or is this something that R should/could
fix? If the latter, could this also go into the "emergency release" R
4.0.2 that is scheduled for 2020-06-22?
My $.02
/Henrik
On Sun, May 31, 2020 at 8:13 AM Gábor Csárdi wrote:
>
> Btw. it would be also possible to create a m
Dear Peter,
Thank you very much for this.
To clarify slightly, the bug affects not just the Rcmdr package but use of the
tcltk package on Windows more generally.
Best,
John
-
John Fox, Professor Emeritus
McMaster University
Hamilton, Ontario, Canada
Web:
Unfortunatly, a memory allocation bug prevented the R Commander package from
working on Windows. This is fixed in R-patched, but we cannot have this not
working in the official release when IT departments start installing for the
Fall semester, so we need to issue a new release.
Full schedule i
Hi Carson,
thanks for the report. This is a bug in R, specific to Windows and to
characters that use surrogate pairs - other characters will work fine,
other recent operating systems where R runs will work fine (all where a
single wchar_t holds complete Unicode characters). Now fixed in R-deve
10 matches
Mail list logo
