Remove inter-server copy language

On Thu, Aug 08, 2013 at 01:41:20PM -0700, Mike Eisler wrote:
> So, I suggest removing references to the copy-related RPCSEC_GSSv3
> privileges from the NFSv4.2 spec. The way to make inter-vserver copy
> secure is implied by:
>
>
> 3.4.1.3. Inter-Server Copy via ONC RPC but without RPCSEC_GSSv3
>
>
> "For example, suppose the network topology is as shown in Figure 3.
>    If the source filehandle is 0x12345, the source server may respond to
>    a COPY_NOTIFY for destination 203.0.113.56 with the URLs:
>
>       nfs://203.0.113.18//_COPY/FvhH1OKbu8VrxvV1erdjvR7N/203.0.113.56/
>       _FH/0x12345
>
>       nfs://192.0.2.18//_COPY/FvhH1OKbu8VrxvV1erdjvR7N/203.0.113.56/_FH/
>       0x12345
>
>    The name component after _COPY is 24 characters of base 64, more than
>    enough to encode a 128 bit random number."
>
>
> So, servers that want to enforce secure inter-server copy simply reject
> COPY_NOTIFY requests that do not use RPCSEC_GSS(v1 or v2) privacy. When
> privacy is used, the URL in the COPY_NOTIFY reply is encrypted.
>
> The client SHOULD then send COPY to the destination with RPCSEC_GSS v1 or
> v2 privacy so that the shared secret is encrypted.

OK, if that's good enough, great.

A very quick attempt follows.

--b.

commit 9b786365d6432462338c7b5425ba2bac22beae32
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Fri Aug 9 11:39:57 2013 -0400

    Remove dependency of server-to-server copy on RPCSEC_GSSv3

    RPCSEC_GSSv3 progress seems stalled, while implementation
    of other features is progressing.

    It appears that the random-cookie-in-a-URL approach could provide
    sufficient security on its own, so recommend that instead.

Signed-off-by: loghyr <loghyr@gmail.com>
Merge branch 'master' of github.com:loghyr/NFSv4.2
Pull in the SSC rewording and tighten up