#rpc #sun #xdr #protocols #remote-procedure #api-bindings #onc

onc-rpc

Open Network Computing / Sun RPC types and fast serialisation

8 releases

0.3.0 May 13, 2024
0.2.5 May 10, 2024
0.2.3 Jun 22, 2021
0.2.2 Jan 1, 2021
0.1.0 Jun 9, 2020

#154 in Encoding

Download history 6/week @ 2024-02-22 8/week @ 2024-02-29 3/week @ 2024-03-07 2/week @ 2024-03-14 10/week @ 2024-03-28 26/week @ 2024-04-04 16002/week @ 2024-04-11 28915/week @ 2024-04-18 14342/week @ 2024-04-25 11736/week @ 2024-05-02 11799/week @ 2024-05-09 20419/week @ 2024-05-16 16102/week @ 2024-05-23 10335/week @ 2024-05-30

60,589 downloads per month

BSD-3-Clause

105KB
2K SLoC

crates.io docs.rs

ONC RPC

This crate implements the Open Network Computing Remote Procedure Call system (originally known as the Sun RPC system) as described in RFC 1831 and RFC 5531.

  • Zero copy deserialisation
  • Support for serialisation buffer reuse and pooling
  • Only safe Rust code
  • No heap allocations
  • Simple, descriptive, one-to-one types matching the RFCs

Example

use onc_rpc::{
    auth::{AuthFlavor, AuthUnixParams},
    CallBody,
    MessageType,
    RpcMessage,
};

// Add RPC call authentication.
let auth_params = AuthUnixParams::new(
	42,										// Stamp
	"bananas.local",						// Machine name
	501,									// UID
	501,									// GID
	None,									// No additional GIDs
);

// Build a dummy byte payload.
let payload = vec![42, 42, 42, 42];

// Construct the actual RPC message.
let msg = RpcMessage::new(
    4242,
    MessageType::Call(CallBody::new(
        100000, 							// Program number
        42,									// Program version
        13,									// Procedure number
        AuthFlavor::AuthUnix(auth_params),	// Credentials
        AuthFlavor::AuthNone(None),			// Response verifier
        &payload,
    )),
);

// Serialise the RPC message, or serialise_into() to reuse buffers.
let network_buffer = msg.serialise().expect("serialise message");

// And do something with it!

Limitations

I had no use for the following, however PRs to extend this crate are happily accepted :)

  • No support for fragmented messages
  • No support for the deprecated and trivially broken Diffie-Hellman authentication flavor
  • No defined GSS / Kerberos auth flavor types

The auth flavors not included in this crate can still be used as the flavor discriminant and associated opaque data is available in the application layer - this crate just lacks pre-defined types to describe them.

Future development

Currently a buffer has to be passed to serialise the complete message into a continuous memory region - it would be nicer to support vectorised I/O to provide zero-copy serialisation too.

Fuzzing

Included in the fuzz/ directory is a deserialisation fuzzer that attempts to decode arbitrary inputs, and if successful serialises the resulting message and compares the result with the input.

Install cargo fuzz and invoke the fuzzer with cargo fuzz run parse_serialise -- -jobs=30 for parallelised workers.

Dependencies

~0.5–1MB
~22K SLoC