From: Bernd Schubert <bernd-schubert@web.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: Problems with statd and lockd
Date: Sun, 6 Apr 2003 15:09:28 +0200 [thread overview]
Message-ID: <200304061509.28615.bernd-schubert@web.de> (raw)
In-Reply-To: <16016.6804.336490.539227@charged.uio.no>
>
> If secure-statd was the cause of the problem, I would expect
> additional messages of the form
>
> "Call to statd from non-local host blah"
>
> or
>
> "Attempt to register callback to 1000xy/z"
>
> or
>
> "Attempt to register host blah (not a dotted quad)"
No, we have never seen anything like this.
> > What problems can be caused by a statd without the secure
> > option ?
>
> People could use your statd to make arbitrary RPC calls.
>
Hmm, though we are protected by a firewall on most ports, I better add a
statd-line to /etc/hosts.allow ;-)
Is there something I can do to debug this problem ?
Best regards,
Bernd
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-04-06 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 23:56 Problems with statd and lockd Philippe Gramoullé
2003-04-05 10:14 ` Trond Myklebust
2003-04-05 11:18 ` Philippe Gramoullé
2003-04-05 11:50 ` Trond Myklebust
2003-04-05 12:05 ` Philippe Gramoullé
2003-04-05 13:45 ` Bernd Schubert
2003-04-05 14:27 ` Trond Myklebust
2003-04-05 16:31 ` Bernd Schubert
2003-04-05 23:06 ` Philippe Gramoullé
2003-04-06 12:16 ` Trond Myklebust
2003-04-06 13:09 ` Bernd Schubert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304061509.28615.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.