Update:
The IT people agreed to test R separately. R is now approved and RStudio
is not.
The folks at RStudio are baffled as to why all those registry entries
are being
recorded. They directed me to the source code which details the known
accesses
to the registry during installation. I have no
how about just removing those network related package (including CRAN) from
your copy of R?
R can be used portably, as long as you have the package you need installed
already within your R.
--
View this message in context:
http://r.789695.n4.nabble.com/registry-vulnerabilities-in-R-tp4619217p463
What about using a Portable Apps style packaging of R? That might solve some
of the issues.
--
View this message in context:
http://r.789695.n4.nabble.com/registry-vulnerabilities-in-R-tp4619217p4623388.html
Sent from the R help mailing list archive at Nabble.com.
___
One more item. Have you given a copy of the document
R: Regulatory Compliance and Validation Issues A Guidance Document
for the Use of R in Regulated Clinical Trial Environments
http://www.r-project.org/doc/R-FDA.pdf
to your security office?
It addresses overlapping, not identical, security
Thanks Rich and Paul:
This gets back to my original comment in this thread. I believe that
CRAN repositories simply rely on whatever security software (malware
checking, etc.) that the hosts provide; R/CRAN do nothing, as you
said. This results in a whole new and almost certainly wholly
impractica
On 09/05/2012 2:04 PM, Gabor Grothendieck wrote:
On Wed, May 9, 2012 at 12:46 PM, Paul Martin wrote:
> I don't have much new to add, but I want to make some clarifying comments:
>
> First, there are clearly workarounds available. I am using one now. R is
> installed on a personal laptop which
I spoke to someone in the military who did some investigation.
This is his response
>> 1. I'm sorry that I don't have anything good to report. The military is
>> cautious with it's networks and I'm no longer able to use R at work. I
>> don't know anything about this registry issue but the show s
On Wed, May 9, 2012 at 12:46 PM, Paul Martin wrote:
> I don't have much new to add, but I want to make some clarifying comments:
>
> First, there are clearly workarounds available. I am using one now. R is
> installed on a personal laptop which I bring to work every day. I take
> extreme care with
I don't have much new to add, but I want to make some clarifying comments:
First, there are clearly workarounds available. I am using one now. R is
installed on a personal laptop which I bring to work every day. I take
extreme care with the nature of the files I move back and forth, and
none o
On May 9, 2012, at 11:00 AM, Barry Rowlingson wrote:
>>> Someone said:
>
>>> Once R is accepted, you could ask for an RStudio test if you want.
>
> I had another thought shortly after my initial email. Suppose yes, R
> is accepted. Great. You run R.
>
> Then you think, "Oh, I need ggplot2" (ye
>> Someone said:
>> Once R is accepted, you could ask for an RStudio test if you want.
I had another thought shortly after my initial email. Suppose yes, R
is accepted. Great. You run R.
Then you think, "Oh, I need ggplot2" (yes you do). Do you then have
to get security clearance for every pac
On May 9, 2012, at 9:57 AM, Duncan Murdoch wrote:
> On 08/05/2012 11:10 AM, Paul Martin wrote:
>>Kirtland Air Force Base has denied approval for the use of R on its
>>Windows network. Some of their objections seem a bit strange, but some
>>appear to be legitimate. In particular, th
Murdoch
Sent: 09 May 2012 15:57
To: pamar...@alum.mit.edu
Cc: r-help@r-project.org
Subject: Re: [R] registry vulnerabilities in R
On 08/05/2012 11:10 AM, Paul Martin wrote:
> Kirtland Air Force Base has denied approval for the use of R on its
> Windows network. Some of their objection
On 08/05/2012 11:10 AM, Paul Martin wrote:
Kirtland Air Force Base has denied approval for the use of R on its
Windows network. Some of their objections seem a bit strange, but some
appear to be legitimate. In particular, they have detected registry
"vulnerabilities"
which
On Tue, May 8, 2012 at 4:10 PM, Paul Martin wrote:
>
> Kirtland Air Force Base has denied approval for the use of R on its
> Windows network. Some of their objections seem a bit strange, but some
> appear to be legitimate. In particular, they have detected registry
> "vulnerabilities"
>
I am totally ignorant on these matters, but ..
R is open source statistical software written largely for (and used a
lot by) academics for research. So I would not be surprised if it has
"security vulnerabilities". As usual, the GPL explicitly exempts the R
organization from any responsibility on
16 matches
Mail list logo
