Your message dated Wed, 30 Apr 2008 12:22:33 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#478564: elinks: Elinks relays on real UID not on 
effective.
has caused the Debian Bug report #478564,
regarding elinks: Elinks relays on real UID not on effective.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
478564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478564
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: elinks
Version: 0.11.3-6
Severity: normal

Seems like elinks uses real UID, so when you start for example elinks
with sudo it uses $HOME of real user, not /root.
Here are steps how to reproduce it:

[EMAIL PROTECTED]:~$ cd && whoami && pwd
ixti
/home/ixti
[EMAIL PROTECTED]:~$ ls -la | grep elinks
drwx------   2 ixti ixti      4096 Апр 30 00:13 .elinks
[EMAIL PROTECTED]:~$ rm -rf .elinks/
[EMAIL PROTECTED]:~$ sudo elinks
[EMAIL PROTECTED]:~$ ls -la | grep elinks
drwx------   2 root root      4096 Апр 30 00:15 .elinks
[EMAIL PROTECTED]:~$ elinks
ERROR at /tmp/buildd/elinks-0.11.3/src/main/interlink.c:329: The call to
connect() failed: 13 (Access denied)
ERROR at /tmp/buildd/elinks-0.11.3/src/main/interlink.c:329: The call to
bind() failed: 13 (Access denied)
ERROR at /tmp/buildd/elinks-0.11.3/src/main/interlink.c:329: The call to
bind() failed: 13 (Access denied)
ERROR at /tmp/buildd/elinks-0.11.3/src/main/interlink.c:329: The call to
bind() failed: 13 (Access denied)
ERROR at /tmp/buildd/elinks-0.11.3/src/main/interlink.c:329: The call to
bind() failed: 13 (Access denied)

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages elinks depends on:
ii  elinks-data            0.11.3-6          advanced text-mode WWW browser - d
ii  libbz2-1.0             1.0.5-0.1         high-quality block-sorting file co
ii  libc6                  2.7-10            GNU C Library: Shared libraries
ii  libexpat1              1.95.8-4          XML parsing C library - runtime li
ii  libgnutls26            2.2.2-1           the GNU TLS library - runtime libr
ii  libgpmg1               1.20.3~pre3-3     General Purpose Mouse - shared lib
ii  libidn11               1.7-1             GNU libidn library, implementation
ii  liblua50               5.0.3-3           Main interpreter library for the L
ii  liblualib50            5.0.3-3           Extension library for the Lua 5.0 
ii  libperl5.8             5.8.8-12          Shared Perl library
ii  libruby1.8             1.8.6.114-2       Libraries necessary to run Ruby 1.
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

elinks recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi Aleksey,

On 08/04/30 00:20 +0500, Aleksey V. Zapparov said ...
> when you start for example elinks
> with sudo it uses $HOME of real user, not /root.

This is a property of sudo and not that of elinks.  elinks just uses what it
gets in $HOME.  For details seem sudo(8), specifically the -H option.

Hence closing this bug.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to