Bug in hsolinkcontrol...

Tom in IT - Fri, 09.10.2009 - 22:07
I stumbled over a bug in hsolinkcontrol, which
also seems to be reported in this pharscape forum post

Bug description:

  • Ubuntu 9.04, with NO(!) resolvconf package installed

  • hsolink 1.0.118 package

  • HSOconnect 1.2.18 beta

  • /etc/resolv.conf is saved to /etc/resolv.conf.hsoc%s.tmp

  • the permissions of the created /etc/resolv.conf.hsoc%s.tmp file are
    660 and root:root

  • when the saved /etc/resolv.conf.hsoc%s.tmp is moved back to /etc/resolv.conf, this file also gets the 660 permissions

  • after that, only root can read /etc/resolv.conf

  • the effect is, that DNS resolution does not work except when you are root

  • installing resolvconf will work around this issue


This can probably be easily fixed, by making sure that the
/etc/resolv.conf.hsoc%s.tmp has the same permissions as the original
/etc/resolv.conf file. Since installing the resolvconf package makes the bug go away, I did not fix the source, but just sent a notice to the author.
No comments – Add Comment – 1 Trackback
Defined tags for this entry:
Related entries by tags:

Trackbacks
Trackback specific URI for this entry

PingBack
Weblog: identi.ca
Tracked: Oct 09, 22:20

Comments
Display comments as (Linear | Threaded)

No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA 1CAPTCHA 2CAPTCHA 3CAPTCHA 4CAPTCHA 5


 
 
Submitted comments will be subject to moderation before being displayed.
 
 

Frontpage - Top level