Re: Bug#743887: ITP: direnv -- A utility to set directory specific environment variables

2014-04-08 Thread Tollef Fog Heen
]] Punit Agrawal 

 Instead of putting every environment variable in your
 ~/.profile, have directory-specific .envrc files for your
 AWSACCESSKEY, LIBRARY_PATH or other environment variables.

Is there any security built into this?  It sounds like a potential
recipe for disaster if code gets run just by entering a directory.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87ppksdj8w@xoog.err.no



Re: Bug#743887: ITP: direnv -- A utility to set directory specific environment variables

2014-04-08 Thread Punit Agrawal
On Tue, Apr 8, 2014 at 2:49 PM, Tollef Fog Heen tfh...@err.no wrote:
 ]] Punit Agrawal

 Instead of putting every environment variable in your
 ~/.profile, have directory-specific .envrc files for your
 AWSACCESSKEY, LIBRARY_PATH or other environment variables.

 Is there any security built into this?  It sounds like a potential
 recipe for disaster if code gets run just by entering a directory.


By default, there is a mechanism to control which .envrc files are
run. As part of creating the directory-specific configuration, the
user has to explicitly run 'direnv allow' for that directory and
.envrc. The configuration file is automatically blocked if changed,
unless edited with 'direnv edit'.

Hope that answers your question.

Cheers,
Punit

 --
 Tollef Fog Heen
 UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cad4boncfucxwbapjrdua9jy_9c8hn3bra5wft_kd8y4yam1...@mail.gmail.com



Re: Bug#743887: ITP: direnv -- A utility to set directory specific environment variables

2014-04-08 Thread Tollef Fog Heen
]] Punit Agrawal 

 On Tue, Apr 8, 2014 at 2:49 PM, Tollef Fog Heen tfh...@err.no wrote:
  ]] Punit Agrawal
 
  Instead of putting every environment variable in your
  ~/.profile, have directory-specific .envrc files for your
  AWSACCESSKEY, LIBRARY_PATH or other environment variables.
 
  Is there any security built into this?  It sounds like a potential
  recipe for disaster if code gets run just by entering a directory.
 
 
 By default, there is a mechanism to control which .envrc files are
 run. As part of creating the directory-specific configuration, the
 user has to explicitly run 'direnv allow' for that directory and
 .envrc. The configuration file is automatically blocked if changed,
 unless edited with 'direnv edit'.

Yes, that sounds pretty reasonable to me.  Thanks for the quick answer.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/m2ioqjkcnz@rahvafeir.err.no



Bug#743887: ITP: direnv -- A utility to set directory specific environment variables

2014-04-07 Thread Punit Agrawal
Package: wnpp
Severity: wishlist
Owner: Punit Agrawal punitagra...@gmail.com

* Package name: direnv
  Version : 2.3.0
  Upstream Author : Jonas Pfenniger
* URL : http://direnv.net/
* License : MIT
  Programming Lang: Go
  Description : A utility to set directory specific environment variables

direnv is a shell extension that loads different environment
variables depending on your path.

Instead of putting every environment variable in your
~/.profile, have directory-specific .envrc files for your
AWSACCESSKEY, LIBRARY_PATH or other environment variables.

It does some of the job of rvm, rbenv or virtualenv but in a language-
agnostic way

I use this tool to set-up different environment variables for the projects
I build.

Javi (cc'd) has agreed to mentor this package and sponsor it when ready.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140407220714.2451.56991.report...@e104195-lin.cambridge.arm.com