On Sun, May 3, 2015, at 11:56, Avinash Sonawane wrote:
> On Sun, May 3, 2015 at 8:24 PM, Avinash Sonawane
> wrote:
> > On Sun, May 3, 2015 at 7:58 PM, Nicolas George wrote:
> >> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> >>> So will it work if I add `authrequired
On Sun, May 03, 2015 at 03:20:05PM +0200, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Jonathan Dowland a écrit :
> > There's nothing wrong with the file permissions. By default, root's
> > shell reads /etc/environment, but users do not. To be honest I'm not
> > sure why that is the
Hi,
Please do not CC me, I am subscribed to the list.
On Sun, May 03, 2015 at 03:36:10PM +0200, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Jonathan Dowland a écrit :
> > This is inevitable with http_proxy, sadly, as there is no one place you can
> > put things that will guarantee
On Sun, May 3, 2015 at 8:24 PM, Avinash Sonawane wrote:
> On Sun, May 3, 2015 at 7:58 PM, Nicolas George wrote:
>> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>>> So will it work if I add `authrequiredpam_env.so`
>>> to lightdm, lightdm-greeter and lightdm-a
On Sun, May 3, 2015 at 7:58 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> So will it work if I add `authrequiredpam_env.so`
>> to lightdm, lightdm-greeter and lightdm-autologin files?
>
> Try.
Awesome! It worked! I added `auth
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> So will it work if I add `authrequiredpam_env.so`
> to lightdm, lightdm-greeter and lightdm-autologin files?
Try.
> So I should file this against jessie, lightdm or xfce(as in GNOME
> /etc/environment was getting
On Sun, May 3, 2015 at 7:15 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> I think I am using lightdm as display manager/login manager. (Any way
>> to find out which is?)
>
> You can probably see what display manager is running with "ps".
Yes. It is
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> I think I am using lightdm as display manager/login manager. (Any way
> to find out which is?)
You can probably see what display manager is running with "ps".
> And in lightdm, lightdm-autologin and lightdm-greeter I see:
>
> # Loa
On Sun, May 3, 2015 at 6:51 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> I am using Jessie with XFCE.
>
> Look in /etc/pam.d/ if there is a file related to xfce and its display
> manager.
$ ls /etc/pam.d
-rw-r--r-- 1 root root 235 Sep 30 2014
Le quartidi 14 floréal, an CCXXIII, Jonathan Dowland a écrit :
> This is inevitable with http_proxy, sadly, as there is no one place you can
> put things that will guarantee that all processes with get them as environment
> variables, and no guarantee that all processes will honour http_proxy anywa
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> I am using Jessie with XFCE.
Look in /etc/pam.d/ if there is a file related to xfce and its display
manager. If there is, check that pam_env.so is invoked. If it is not, add it
by imitating another file that does it right (xdm for ex
Le quartidi 14 floréal, an CCXXIII, Jonathan Dowland a écrit :
> There's nothing wrong with the file permissions. By default, root's
> shell reads /etc/environment, but users do not. To be honest I'm not
> sure why that is the case.
I believe you are wrong.
> You can configure your user(s) to sou
I am using Jessie with XFCE.
When I try to invoke any network using utility as normal user my
/etc/environment is not getting used as if for normal user
/etc/environment doesn't exist. While when I try to invoke the same
utility as a root user the proxy set in /etc/environment just works as
if /et
On Sun, May 03, 2015 at 05:09:20PM +0530, Avinash Sonawane wrote:
> may be it's file permissions. For me
> $ ls -la /etc/environment /etc/sudoers
> -rw-r--r-- 1 root root 117 May 2 17:41 /etc/environment
> -r--r- 1 root root 778 May 3 16:13 /etc/sudoers
There's nothing wrong with the file pe
On Sun, May 03, 2015 at 11:59:29AM +0200, Nicolas George wrote:
> On the other hand, that means that the HTTP proxy would be configured at two
> different places. This is rarely a good idea, because one day the
> configuration will change, and one of the places will be forgotten.
This is inevitabl
On Sun, May 3, 2015 at 4:54 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> No. Sorry for not being so clear. When I say `$ env` (i.e. as normal
>
> Do not worry, everyone forgets to check basic things from time to time.
>
>> user) it doesn't show http
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> No. Sorry for not being so clear. When I say `$ env` (i.e. as normal
Do not worry, everyone forgets to check basic things from time to time.
> user) it doesn't show http_proxy. As if /etc/environment is not
> available to normal use
Here is something. When I say `$ wget http://foobar` (normal user)
then it says unable to resolve (proxy doesn't work) but when I say `#
wget http://foobar` (root user) the resource gets downloaded (proxy
works)
So I think the real problem is /etc/environment is not getting used
for normal user wh
On Sun, May 3, 2015 at 4:27 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> When I say `# env` I can see http_proxy=http://192.168.6.254:3128 but
>> when I say `$ sudo env` there's no http_proxy variable printed.
>>
>> What's going on?
>
> I assume tha
Avinash Sonawane writes:
> > %sudo ALL=NOPASSWD: ALL
>
> What does this line do? NOPASSWD?
it means that if someone is in sudo group, sudo command does not ask
password.
-- juha
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
On Sun, 3 May 2015 16:24:15 +0530
Avinash Sonawane wrote:
> On Sun, May 3, 2015 at 3:58 PM, Juha Heinanen wrote:
>
> > %sudo ALL=NOPASSWD: ALL
>
> What does this line do? NOPASSWD?
It lets you run commands as another user (normally root) without
entering your password.
Petter
--
"I'm ioniz
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> When I say `# env` I can see http_proxy=http://192.168.6.254:3128 but
> when I say `$ sudo env` there's no http_proxy variable printed.
>
> What's going on?
I assume that you checked that "env" without "sudo" shows http_proxy?
If s
On Sun, May 3, 2015 at 3:58 PM, Juha Heinanen wrote:
> %sudo ALL=NOPASSWD: ALL
What does this line do? NOPASSWD?
--
Avinash Sonawane (RootKea)
PICT, Pune
http://www.rootkea.wordpress.com
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
On Sun, May 3, 2015 at 4:09 PM, Nicolas George wrote:
> Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
>> > 2) Move 'Defaults env_keep…' to line 12 in /etc/sudoers (i.e. *before*
>> > "User privilege escalation section")
>> Same error. Here's my updated /etc/sudoers http://paste.de
Le quartidi 14 floréal, an CCXXIII, Avinash Sonawane a écrit :
> > 2) Move 'Defaults env_keep…' to line 12 in /etc/sudoers (i.e. *before*
> > "User privilege escalation section")
> Same error. Here's my updated /etc/sudoers http://paste.debian.net/170961/
The "env_keep" directive it still at the e
On Sun, May 3, 2015 at 2:50 PM, Reco wrote:
> 2) Move 'Defaults env_keep…' to line 12 in /etc/sudoers (i.e. *before*
> "User privilege escalation section")
Same error. Here's my updated /etc/sudoers http://paste.debian.net/170961/
I think this might be relevant. I had previous configuration whi
In my jessie, 'sudo apt-get update' works fine without any special
tricks:
$ sudo apt-get update
Get:1 http://ftp.fi.debian.org jessie InRelease [128 kB]
...
My sudoers is below. I have changed only one line from the default.
-- Juha
#
# This file MUST be edited with the 'visudo' command as r
Le quartidi 14 floréal, an CCXXIII, Jonathan Dowland a écrit :
> The safest way would be a variation on 3), IMHO
>
> echo 'Acquire::http::Proxy "http://192.168.6.254:3128";;' | \
> sudo tee -a /etc/apt/apt.conf.d/90http-proxy
>
> This should make the setting persist and normal apt-get updat
On Sun, May 03, 2015 at 12:20:35PM +0300, Reco wrote:
> 1) sudo -E apt-get update
>
> 2) Move 'Defaults env_keep…' to line 12 in /etc/sudoers (i.e. *before*
> "User privilege escalation section")
>
> 3) sudo apt-get -o Acquire::http::Proxy=http://192.168.6.254:3128 update
The safest way would be
e should
> add `
> Defaults env_keep += "ftp_proxy http_proxy https_proxy no_proxy"` to
> /etc/sudoers (the recommended way according to arch wiki).
>
> So I changed my /etc/sudoers. Here is it http://paste.debian.net/170961/
>
> But still `$ sudo apt-get update` produce
ged my /etc/sudoers. Here is it http://paste.debian.net/170961/
But still `$ sudo apt-get update` produces above error. And it's
really an inconvenience for me to become root user to do apt thing.
So why `sudo` not respecting `/etc/sudoers` ? Am I missing something?
Thank you.
--
Avinas
31 matches
Mail list logo
