Re: [Proftpd-devel] RUN_DIR vs PR_RUN_DIR, adding /proftpd to them

[Matus U. - f. <uh...@fa...>]

On 13.05 09:15, TJ Saunders wrote:
> > Build scripts use to change when new version of ProFTPD is available, e.g.
> > because new modules are added, and people or scripts should not blindly
> > assume that the same configure options may cause the same behaviour.
> 
> There is a difference betwee adding new features, and changing existing
> ones.  And simply because "people should not blindgy assume" things does
> not stop them from doing just that.

yes, but fixing bugs often causes removing some features ;)

> > I consider this behaviour as a bug, because it makes impossible to specify
> > exact directory where such files should be located (without patching
> > confnigure.in).
> 
> I do not consider this a bug, because there are configuration directives
> for configuring the exact locations of all of proftpd's files.

Yes, but ftpwho, ftptop and ftpdctl ocasionally can't read config file
(ftpwho and ftptop do have the functionality, while ftpdctl does not),
possibly of security reasons, e.g. user that is allowed to see logged users
is not allowed to see ftpd config (and SQL passwords)

Having those programs setgid (and patching ftpdctl to read config file)
would help a bit, but currently I still "need" one subdirectory I do not
want.

OTOH:
patching configure, or adding it an option to get rid of that is imho
worse than changind it to use exactly what user provided.

And you probably didn't think about users that specified /var/run(/proftpd)
in the past, wondered why it adds /proftpd to that directory and did not
report it.

-- 
Matus UHLAR - fantomas, uh...@fa... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization.