On Thu, Aug 19, 2021 at 04:25:34PM +, Andy Smith
wrote:
> Hello,
>
> On Tue, Aug 17, 2021 at 11:17:05AM +1000, raf wrote:
> > I just noticed many many sshd segfaults listed in
> > /var/log/kern.log. There are two versions. They look
> > like this:
> >
> > sshd[1086]: segfault at 7fff615e
Hello,
On Tue, Aug 17, 2021 at 11:17:05AM +1000, raf wrote:
> I just noticed many many sshd segfaults listed in
> /var/log/kern.log. There are two versions. They look
> like this:
>
> sshd[1086]: segfault at 7fff615eaec8 ip
> 7ff2a586f42f sp 7fff615eaed0 error 6 in
> libwrap.so.0.7.
e are many because
it's a cronned backup.
I am using /etc/hosts.allow for sshd and have a mixture
of IPv4 and IPv6 addresses in it.
When I added the IPv6 address in question to
/etc/hosts.allow, the segfaults stopped and the
connections worked.
This started 2 days before I upgraded to debian11
Has anything relating to those files changed between jessie and stretch
to affect cups being blocked?
Would a line in the allow file ALL: localhost:631 help or is the syntax
incorrect?
Hello Clive
Thanks for pointing me to to ipcalc,
I noticed smb.conf has a commented entry for 127.0.0.0/8
This would cover the whole local subnet:
HostMin: 127.0.0.1
HostMax: 127.255.255.254
Does it make sense to cover more than 127.0.0.1 and 127.0.1.1 in
/etc/hosts.allow ?
I don&#
Thanks for clearing this up Juan and Shawn.
I noticed I could change smbd to run in inetd mode if I flip the switch
in /etc/default/samba, but I don't known how this would improve things,
eventually create new drawback in cifs performance ... so I'll keep it
as it is with additional smb.conf e
Hi Tuxoholic,
[...]
> With this smb.conf tweaking it works fine, but why could smbd/nmbd run past
> /etc/hosts.allow and /etc/hosts.deny without those lines in smb.conf?
Already answered by Juan Sierra Pons.
> To my limited CIDR understandig a /32 mask should restrict
ME localhost.localdomain localhost
> > 127.0.1.1 MYHOSTNAME
> > 192.168.2.10MYSERVER
> >
> > cat /etc/hosts.allow
> > #ALL: localhost 127.0.1.1 192.168.2.0/24
> > ALL: localhost 127.0.1.1 192.168.2.0/32
> >
> > /etc/hosts.deny
> >
hosts allow = 192.168.2.0/32, 127.
> hosts deny = ALL
>
> With this smb.conf tweaking it works fine, but why could smbd/nmbd run past
> /etc/hosts.allow and /etc/hosts.deny without those lines in smb.conf?
>
> To my limited CIDR understandig a /32 mask should restrict acces
hi list
Can somebody explain why smbd and nmbd are not affected by the following
strict ruleset in /etc/hosts* ?
/etc/hosts
127.0.0.1 MYHOSTNAME localhost.localdomain localhost
127.0.1.1 MYHOSTNAME
192.168.2.10MYSERVER
cat /etc/hosts.allow
#ALL: localhost 127.0.1.1 192.168.2.0
On Thu, 7 Nov 2002, Benedict Verheyen wrote:
> Hi,
>
> i have some problems setting up ssh connection (not the scope of this email though
>not yet :-) and i came across the /etc/hosts.allow & /etc/hosts.deny files.
>
> Now, i saw in some documents about ssh that they
On Thu, Nov 07, 2002 at 12:18:09PM +, Benedict Verheyen wrote:
> Now, i saw in some documents about ssh that they add "sshd: all" to the
> /etc/hosts.allow file. Am i correct that these 2 files are only used
> when you have inetd enabled and that they otherwise serve no
Hi,
i have some problems setting up ssh connection (not the scope of this email though not
yet :-) and i came across the /etc/hosts.allow & /etc/hosts.deny files.
Now, i saw in some documents about ssh that they add "sshd: all" to the
/etc/hosts.allow file. Am i correct that the
> The server needs the following daemons running:
> portmap, nfs-common, nfs-server
> The client needs portmap and nfs-common
>
> My question is, can you mount the nfs share remotely
> when the entry in /etc/hosts.deny is removed, and in /etc/hosts.allow you
> put "ALL:
mount the nfs share remotely
when the entry in /etc/hosts.deny is removed, and in /etc/hosts.allow you put
"ALL: ALL"?
I would suggest using ipchains to block nfs and rpc from the outside, like
this, where 192.168.1.1 is your machines **external** interface (i.e., the
one connected to
> I'm too lame to find out how to re-start portmap. And rebooting didn't fix
> it.
/etc/init.d/portmap restart
mek
> Did you re-start portmap after adding that line? That should fix it.
>
> noah
I'm too lame to find out how to re-start portmap. And rebooting didn't fix
it.
On Tue, Apr 10, 2001 at 11:39:44AM +0200, Robert Voigt wrote:
> To allow the other machine on the LAN access to mine again I put the line
> portmap: 192.168.1.0/255.255.255.0
> in /etc/hosts.allow
> but the other machine still can't mount anything. It gets the error message
>
AN, and
I hope this will prevent anyone from the outside world to break into my
system, because that's why I do it.
To allow the other machine on the LAN access to mine again I put the line
portmap: 192.168.1.0/255.255.255.0
in /etc/hosts.allow
but the other machine still can't mount a
> "KMS" == Karsten M Self writes:
KMS> on Sat, Mar 24, 2001 at 04:18:09PM -0700, Mike Millner ([EMAIL
PROTECTED]) wrote:
>> When I make changes to files, for example hosts.deny or
>> hosts.access how do I get the OS to see them without rebooting?
KMS> The issue is not the OS
on Sat, Mar 24, 2001 at 04:18:09PM -0700, Mike Millner ([EMAIL PROTECTED])
wrote:
> When I make changes to files, for example hosts.deny or hosts.access
> how do I get the OS to see them without rebooting? I know with my DNS
> files I can do a "rndc reload" and the changes are read but with these
21 matches
Mail list logo
