On 18 December 2011 at 16:16, Simon Urbanek wrote:
| Barry,
|
| that's a great idea. I have created a package that allows you to read/write
passwords to user's keychain:
|
| http://www.rforge.net/keychain
|
| So far it uses the Security framework so you'll need a Mac, it but I'm about
to add
Barry,
that's a great idea. I have created a package that allows you to read/write
passwords to user's keychain:
http://www.rforge.net/keychain
So far it uses the Security framework so you'll need a Mac, it but I'm about to
add a generic fall-back system (encrypted file on-disk) and possibly t
On Sun, Dec 18, 2011 at 1:28 AM, Paul Gilbert wrote:
> One way this is often done is to have this information in a file that only
> the owner can read. For example, mysql uses a file .my.cnf (in Windows it
> may have a different name). The code then just reads the information from
> the file. To g
One way this is often done is to have this information in a file that
only the owner can read. For example, mysql uses a file .my.cnf (in
Windows it may have a different name). The code then just reads the
information from the file. To guard against user carelessness, I think
mysql will not use
On Wed, Dec 14, 2011 at 9:54 PM, Ni Wang wrote:
> hi, r developers, I am now working on a R function/package to handling
> online request with username and token/password.
>
> For security reasons, it's not so safe to store the username & token in
> persistent variables, since they'll be saved to
hi, r developers, I am now working on a R function/package to handling
online request with username and token/password.
For security reasons, it's not so safe to store the username & token in
persistent variables, since they'll be saved to disk when
users save their workspace. Is there a secure wa
