Bug#409345: hylafax-server: Clarify accounts, privileges, and file ownership and modes

2008-12-03 Thread Olivier
hello,

I'll second original poster demand as we don't have clue about how to edit
config files.
What does this servertracing value mean, for instance ?

Regards


Bug#409345: hylafax-server: Clarify accounts, privileges, and file ownership and modes

2007-02-03 Thread Ross Boylan
On Fri, Feb 02, 2007 at 09:58:54AM +0100, Giuseppe Sacco wrote:
[...]
  Background: I attempted to send a fax and got (on the client matchine)
  Service not available, remote server closed connection
  421 Timeout (900 seconds): closing control connection.
  Document transfer failed: 421 Timeout (900 seconds): closing control
  connection.
  
  Yet my hfaxd.conf has
  IdleTimeout: 2000
  
  My hfaxd.conf had root as owner and group, with only owner allowed to
  read.  So I presume hfaxd couldn't read it, and used its default value
  instead.  I don't seem any log messages confirming this, and I don't
  know that my fix of changing the owner to uucp worked.  If it didn't,
  there might be another bug in here.
 
 what is your servertracing value in /etc/hylafax/config ?
No value is set in config.  There is a value in hfaxd.conf, but not
only is that in the file it didn't seem to be reading, but it's 
0x001.

Ross


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409345: hylafax-server: Clarify accounts, privileges, and file ownership and modes

2007-02-02 Thread Ross Boylan
Package: hylafax-server
Version: 2:4.3.1-6
Severity: wishlist

I ran into a problem that I believe was the result of bad
ownership/permissions of some configuration files.  To verify that, I
attempted to determine what the intended ownership and mode of the
file was and what user hylafax (in particular hfaxd) ran as.

I've been unable to get a definite answer from the man pages,
hylafax-doc, or the hylaFAQ online, and I've seen some contradictory
and clearly incorrect information as well.  Some documents referred to
hylafax running as root, fax, or faxmaster.  man hosts.hfaxd says it
must be mode 600 and owned by the fax user.

On my system it is mode owner read only, uucp as owner.  hfaxd seems
to be running as uucp, though the binary is root and the init.d script
does not set a user.  So I assume it changes to its user after it
runs.

README.Debian does include some discussion of mail accounts (thank
you), but the issues above are a bit different.

The reason this all matters is that sometimes while editing one
inadvertently changes ownership or mode (using RCS under emacs has a
nasty habit of doing this), and it would be nice to know how things
were supposed to be.

Background: I attempted to send a fax and got (on the client matchine)
Service not available, remote server closed connection
421 Timeout (900 seconds): closing control connection.
Document transfer failed: 421 Timeout (900 seconds): closing control
connection.

Yet my hfaxd.conf has
IdleTimeout: 2000

My hfaxd.conf had root as owner and group, with only owner allowed to
read.  So I presume hfaxd couldn't read it, and used its default value
instead.  I don't seem any log messages confirming this, and I don't
know that my fix of changing the owner to uucp worked.  If it didn't,
there might be another bug in here.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages hylafax-server depends on:
ii  adduser  3.101   Add and remove users and groups
ii  debconf [debconf 1.5.11  Debian configuration management sy
ii  gs   8.54.dfsg.1-5   Transitional package
ii  gs-esp [gs]  8.15.3.dfsg.1-1 The Ghostscript PostScript interpr
ii  gs-gpl [gs]  8.54.dfsg.1-5   The GPL Ghostscript PostScript int
ii  hylafax-client   2:4.3.1-6   Flexible client/server fax softwar
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-21  GCC support library
ii  libpam0g 0.79-4  Pluggable Authentication Modules l
ii  libstdc++6   4.1.1-21The GNU Standard C++ Library v3
ii  libtiff-tools3.8.2-7 TIFF manipulation and conversion t
ii  libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra
ii  lsb-base 3.1-22  Linux Standard Base 3.1 init scrip
ii  mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii  metamail 2.7-52  implementation of MIME
ii  psmisc   22.3-1  Utilities that use the proc filesy
ii  sed  4.1.5-1 The GNU sed stream editor
ii  sharutils1:4.2.1-15  shar, unshar, uuencode, uudecode
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages hylafax-server recommends:
ii  metamail  2.7-52 implementation of MIME

-- debconf information:
* hylafax-server/configure_note:
  hylafax-server/attachment:
  hylafax-server/start_now: true
  hylafax-server/setup_failed:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409345: hylafax-server: Clarify accounts, privileges, and file ownership and modes

2007-02-02 Thread Giuseppe Sacco
Il giorno ven, 02/02/2007 alle 00.08 -0800, Ross Boylan ha scritto:
[...]
 I ran into a problem that I believe was the result of bad
 ownership/permissions of some configuration files.  To verify that, I
 attempted to determine what the intended ownership and mode of the
 file was and what user hylafax (in particular hfaxd) ran as.

The uid used by hylafax on Debian is uucp. This is written into hylafax
code, so that when the server run, it change uid and switch chroot
to /var/spool/hylafax. This is why all configuration files are copied
there. The copy will check that ownership is unchanged.

[...]
 Background: I attempted to send a fax and got (on the client matchine)
 Service not available, remote server closed connection
 421 Timeout (900 seconds): closing control connection.
 Document transfer failed: 421 Timeout (900 seconds): closing control
 connection.
 
 Yet my hfaxd.conf has
 IdleTimeout: 2000
 
 My hfaxd.conf had root as owner and group, with only owner allowed to
 read.  So I presume hfaxd couldn't read it, and used its default value
 instead.  I don't seem any log messages confirming this, and I don't
 know that my fix of changing the owner to uucp worked.  If it didn't,
 there might be another bug in here.

what is your servertracing value in /etc/hylafax/config ?

Bye,
Giuseppe



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]