Re: [Denyhosts-user] Why are there entries in hosts-restricted when no restricted-usernames

[Daniel S. <da...@ch...>]

>>>>>> "DS" == Daniel Sutcliffe <da...@ch...> writes:
> DS> I realized after I sent the above that the fact that systemd has
> DS> become almost ubiquitous is making it harder and harder to support
> DS> packages for EL6 and earlier and was thus am a lot less surprised
> DS> than I was when I first found this discrepancy.

On Wed, Sep 30, 2015 at 7:38 PM, Jason L Tibbitts III <ti...@ma...> wrote:
> Well, initscripts aren't that hard.

This is very true, but when they have been removed from the
spec/src.rpm it makes the task more than the trivial tweaking and
rebuilding.

> It's more about me not being able to remember what ancient python
> version is on which EL release, as well as having no way to actually test
> the package.

That is always the headache, made easier in these days of
virtualization, but when it comes down to it there are just not enough
hours in the day.

> The Fedora package will be using python3 once I get it updated, which
> cuts out EPEL (though EPEL7 does have some of python3 at this point).

denyhosts 3 being focussed on python3 might explain the issue I am
currently seeing, but it might also just be a dependency thing. The
process runs for a bit and then falls over with some complaint about
TupleType ... This is probably not the thread or the place to really
discuss this though, this being the defunct denyhosts projects mailing
list. Where is the active forum/list for discussions on the new
GitHub/SFdenhost?

> DS> I have just managed to produce a denyhosts-3.0-0.el6.noarch.rpm so
> DS> soon enough I shall have a better idea if my original issues are
> DS> going to be improved by this later version of denyhosts.
>
> Well, if you want to maintain denyhosts there, feel free to sign up.  I
> can click all of the necessary buttons to give you access.

I have no problem making my specs and RPMs available publically, not
sure how qualified they'll be to actually have them live in EPEL but
lets getting a working RPM first and think about where the spec
belongs later. I do welcome the opportunity to contribute to denyhosts
and/or EPEL whatever.

Back on topic: although my 3.0 install isn't exactly fully functional
yet, I can already see that hosts-restricted is still getting 0 count
entries for attempted logins that aren't anything to do with
restricted-usernames - and checking the AGE_RESET_ bit of code I
suspect is causing this does not seem to contain any changes...

Let's continue this discussion in a more relevant place though, please advise,
Cheers
/dan
-- 
Daniel Sutcliffe <da...@ch...>
Chair Four Development Group LLC