From: Pavel Fedin <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: RE: Bringing up NFS server on 64 bits
Date: Fri, 10 Jan 2014 14:29:00 -0000 [thread overview]
Message-ID: <002301cf0e10$6c1ed7e0$445c87a0$%fedin@samsung.com> (raw)
In-Reply-To: <20140110135208.GG10296@calimero.vinschen.de>
Hello!
> Thanks for working on that. It's highly appreciated. Did you already
> make yourself familiar with Cygwin package maintainance(*)?
Yes, i did. However, perhaps you'll call me a bad guy, but the answer to the first question:
* Do you have the time to maintain the package?
is "sorry, but likely no". I happen to have time only episodically. What obligations does this put on me exactly ? For example, does this mean that i must keep the package up to date and sync up with the mainstream ?
Actually i have come into this only because i sometimes need NFS server myself. I work with embedded Linux systems, and sometimes i boot them up over NFS.
> (3) sounds right to me. As for NIS, I don't think this is important,
> especially not for the NFS server. In theory the OS (Windows)
> decouples the NFS server from having to look for NIS stuff by itself.
> Account info should be available via the OS (Cygwin) calls anyway and
> worse, assuming the NFS server fetches info directly via NIS, the
> entire user/group -> uid/gid -> SID mapping might be screwed up.
No, this doesn't have anything to do with NFS server at all. It's about rpcbind, transport-independent replacement for portmap.
I have examined ONC docs on Oracle's web site and now i have a little clue about this magic code. portmapper has a capability to perform indirect calls. This means that instead of querying for port number and sending direct request to the program you want to talk with, you can ask portmapper to do this instead of you. This code forcibly disables indirect calls for some things which were considered too dangerous by the author. However it looks like the whole ONC RPC is a security nightmare by design.
By the way, does anybody know who is the original author of this NFS server ? Where is upstream repository ? I failed to find one.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-01-10 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:36 Pavel Fedin
2014-01-10 13:52 ` Corinna Vinschen
2014-01-10 14:29 ` Pavel Fedin [this message]
2014-01-10 15:07 ` Corinna Vinschen
2014-01-13 5:48 ` Pavel Fedin
2014-01-13 6:29 ` marco atzeri
[not found] ` <003101cf1031$c11cb640$435622c0$%fedin@samsung.com>
2014-01-13 8:11 ` marco atzeri
2014-01-13 9:24 ` Corinna Vinschen
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='002301cf0e10$6c1ed7e0$445c87a0$%fedin@samsung.com' \
--to=p.fedin@samsung.com \
--cc=cygwin@cygwin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).