Bug 131036

Summary:	Hylafax hosts.hfaxd and SUSE 10 issue
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	J blamson <trout_256>
Component:	Other	Assignee:	Karsten Keil <karsten.keil>
Status:	VERIFIED WORKSFORME	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	i586
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description J blamson 2005-10-27 15:30:25 UTC

Hello,

I have been using SUSE 9.1 before I decided to start using SUSE 10.0. SUSE 10.0 is fantastic!

Now the problem: In the hosts.hfaxd file (SUSE 9.1), the user can enter an IP address in this format 192/.168/.2/.::: and that will allow all valid clients from 192.168.2.XXX to login and fax (obviously the IP numbers can be different, this is just for the example). I have used this setup before with SUSE 9.1, Hylafax, and WHFC. It works perfectly!

Unfortunately, this does not work in SUSE 10.0 (at least I cannot figure out how to make it work with 10.0). Setting up the hosts.hfaxd file exactly the same way as before does not work. I can enter, say, 192.168.2.105 (specific client) and connect without requiring a password, but I cannot setup an entire range as before (i.e. 192/.168/.2/.::: does not allow clients to logon without requiring a password as before).

Please help! Thanks very much!

Comment 1 Michael Gross 2005-10-28 13:44:52 UTC

Might be a bug, or the syntax could have been changed.
Karsten: Please enlighten us.

Comment 2 Karsten Keil 2005-10-31 12:58:33 UTC

The format has be restricted because security issues (for details see bug #64550) and is described in the documentation (e.g. man hosts.hfaxd)
Here some hints:
For example, hosts.hfaxd entries that may be common are

  192.168.0
  username:uid:pass:adminpass
  user@host

After updating, these entries will need to be changed in order to
continue to function.  Respectively, the correct entries should be

  192.168.0.[0-9]+
  username@:uid:pass:adminpass
  user@host

Unless such maching of "username" with "otherusername" and "host" with
"hostname" is desired, the proper form of these entries should include
the delimiter and markers like this

  @192.168.0.[0-9]+$
  ^username@:uid:pass:adminpass
  ^user@host$

So 192/.168/.2/.::: is invalid and should be
@192.168.2.[0-255]+$

Comment 3 Karsten Keil 2005-11-02 20:52:43 UTC

A more correct string is:
@192.168.2.[0-9]+$