Displaying 20 results from an estimated 1000 matches similar to: "2.2.1 to 2.4.1 migration (allowfrom/tcp_wrappers)"
2004 Oct 31
2
[Bug 948] high CPU in sshd after tcp_wrappers deny
http://bugzilla.mindrot.org/show_bug.cgi?id=948
Summary: high CPU in sshd after tcp_wrappers deny
Product: Portable OpenSSH
Version: 3.9p1
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-bugs at mindrot.org
ReportedBy:
2009 Sep 14
1
Fwd: NUT and removed allowfrom/ACCEPT/REJECT support
I don't reply to messages send to me in private.
Best regards, Arjen
--
Please keep list traffic on the list
-------------- next part --------------
An embedded message was scrubbed...
From: Rudolf Cejka <cejkar op fit.vutbr.cz>
Subject: NUT and removed allowfrom/ACCEPT/REJECT support
Date: Mon, 14 Sep 2009 19:23:17 +0200
Size: 3148
URL:
1998 Aug 05
6
Problem with TCP_wrappers
Hi,
I''m running into something weird here.
I''m using RH5.1 with tcp_wrappers 7.6.
The syntax for hosts.allow and hosts.deny is:
<service list> : <access list> [ : <shell_command> ]
Everything works when I _don''t_ use the shell_command.
I used the _exact_ line as in the man-pages utilising "safe_finger" (comes
with tcp_wrappers), tcpdchk
2010 Dec 03
1
[PATCH] upsd tcp_wrappers parsing and logging
Parsing bug was discussed here:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-September/006230.html>
Parsing bug summary
-------------------
working /etc/hosts.allow:
upsd 127.0.0.1 [::1] : ALLOW
broken in /etc/hosts.allow:
upsd localhost : ALLOW
It looks like upsd originally intended to match nut username with system
username? This is not the case now. This causes
2011 Mar 10
1
Access restriction on Upgrade Debian lenny -> Debian squeeze
Hi,
In Debian lenny I used the following in upsd.conf:
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACL webinterface 192.168.0.2/32
ACL slave 192.168.50.22/32
ACCEPT localhost
ACCEPT webinterface
ACCEPT slave
REJECT all
and in upsd.users:
[monmaster]
password = secret0
allowfrom = localhost
upsmon master
[monslave]
password = secret1
allowfrom =
2011 Mar 10
1
Problems with upscmd ACCESS-DENIED
I'm trying to execute some commands on my ups, but I keep getting ERR
ACCESS-DENIED
upscmd -l sinus
Instant commands supported on UPS [sinus]:
beeper.toggle - Toggle the UPS beeper
load.off - Turn off the load immediately
load.on - Turn on the load immediately
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop -
2000 Oct 07
2
[PATCH]: Add tcp_wrappers protection to port forwarding
Hi,
attached is a patch by Chris Faylor <cgf at cygnus.com> relative to
2.2.0p1.
Description:
OpenSSH does not allow port gatewaying by default. This means that only
the local host can access forwarded ports. Adding "GatewayPorts yes" to
.ssh/config usually does this job.
Unfortunately, OpenSSH does not recognize the same hosts.allow/
hosts.deny options as ssh.com's sshd
2006 Aug 07
0
The new formalism : you can try it
Hi ups-dev !
I bring you some news about my work : it works ^_^
you can now try out the new configuration formalism. I modified upsd,
the drivers and upsmon to use the new formalism and the new parser
(via the libupsconfig library)
The SVN link :
svn co svn://svn.debian.org/nut/branches/JD-NewConf
How to use it :
To test it, I propose that you execute the following commands :
Go to the
2014 Mar 23
1
[CentOS} Does anyone use tcp_wrappers?
Most certainly YES!!!
Next to iptables tcp_wrappers is a solid seconde line of defense.
The argument that is is no longer developped is rubbish.
The package does what is should do, functionality isexactly what it
should be and it is bug free.
Also it is flexible enough to do other tricks with it like spawning
something depending on the ip address the incoming connection is coming
from.
It is a
2009 Jun 21
1
tcp_wrappers
Hi,
I've just started using Dovecot (v1.1.14), and I'm noticing a lot of dictionary
attacks. I searched through the documentation and the mailing list archives
hoping to find support for tcp_wrappers (hosts.deny) support.
I did find some suggested patches in the list from last year, but as far
as I can tell, there is no support in the released versions.
Is this implemented and
2009 Mar 07
3
"Master privileges unavailable on UPS" after upgrade to Debian Lenny
Hi all,
I've just upgraded my debian box from etch to lenny, and am now having
Nut problems. I have read through the UPGRADING text (which helped
fixed my first ups driver related problem), but have now hit another
problem, which seems quite common, but non of the responses I've found
on Google apply, so I'm coming to you for help.
On issuing a "/etc/init.d/nut start"
2001 Mar 28
0
Problem with tcp_wrappers
Hello,
I have just found little bug in OpenSSH's tcp_wrappers handling.
In file sshd.c you can find:
if (!hosts_access(&req)) {
close(sock_in);
close(sock_out);
refuse(&req);
}
If username was not requierd for authorization (for example
you are refusing all connection from specific
2006 Jan 09
2
Master privileges unavailable
Hi,
I'm using debian sarge on my server and connected a MGE-ups ellipse via
the serial port.
I searched the internet for the answer, but can't find it.
My config files:
<upsd.users>
[admin]
password = pwd
allowfrom = 127.0.0.1/32
actions = set
instcmds = all
[upsmon]
password = pwd
allowfrom = 127.0.0.1/32 10.0.0.224/32
upsmon master
[upsslave]
password
2006 Aug 14
0
UPS inform GUARD install problem
Hello!
I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is
inform
GUARD series
line interactive UPS
This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv.
The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have one
2006 Aug 14
1
UPS problem
Hello!
I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is
inform
GUARD series
line interactive UPS
This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv.
The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have
2006 Jun 05
0
Passwords not verified in upsmon?
Hy list,
first of all - yes I have read the docs, but obvious I must have missed
something. The user/password setting in upsd.users seems to be ignored
and I can monitor the ups with some arbitrary password.
The following setup is working:
Server A has nut installed and has the following config:
upsd.conf:
ACL localnets 192.168.101.0/255.255.255.0
ACL localhost 127.0.0.1/32
ACL all
2010 Oct 31
2
Problem with monitoring
Dears,
I have centos 5.5 with kernel 2.6.18
UPS: Mustek PowerMust 2000VA USB
I trying to setup monitoring for this ups, I connect ups with server via COM
port and USB.
But here is the problem (with megatec_usb):
[root at optimus ups]# /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.0-
Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb]
Carlos
2010 Oct 30
1
Problem with starting nut
And sorry, I forgot to put log from messages, I always got this:
Oct 30 21:06:25 optimus kernel: usb 5-1: usbfs: process 9808 (megatec_usb)
did not claim interface 0 before use
From: nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org
[mailto:nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org] On
Behalf Of Vladimir Micovic
Sent: Saturday, October 30, 2010 8:00
2017 Jan 09
2
NUT Client shuts down when performing runtime calibration on APC UPS
Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 :
Normal: ups.status: OL
No wall power: ups.status: OB
Runtime calibration (started from AP9630 web interface): ups.status: OB CAL
So at this stage there is a difference!
I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power
2008 Mar 20
1
NUT behaviour when master system fails
Hi all,
We have recently bought an APC UPS and are in the process of setting up
the NUT software to make use of it. We are experiencing a problem with
the behaviour of the slave systems when the master system goes off line.
Although the failure of our master system will (hopefully) be a rare
event, and we hope not to experience too many power outages, it is
possible (if unlikely) that both