jmcph4/nettlesoup

Rusty TFTP

NettleSoup

NettleSoup is a TFTP implementation written in stable Rust.

nettlesoup's Issues

Define message types

RFC 1350 defines five different message types - types need to be defined for these.

• Read Request (RRQ)
• Write Request (WRQ)
• Data (DATA)
• Acknowledgement (ACK)
• Error (ERROR)

Add multiple binary targets

The Cargo project requires two binary targets: one for the server and one for the client.

• Server (tftpd)
• Client (tftpclient)

Define server's CLI

tftpd's invocation should resemble:

tftpd -l 127.0.0.1 -p 69 -v -s

Define connection types

Define Connection and related types (for example, TIDs, as per the RFC).

Write unit tests for message parsing code

Currently, the message parsing code (i.e. the conversion methods to_bytes and from_bytes for the Message trait) present the largest attack surface against tftpd (and the client also).

Unit tests are required for all message parsing code, covering the following test cases:

RRQ

• Mismatched opcode
• Missing filename
• Unterminated filename
• Missing mode string
• Unterminated mode string
• Unterminated filename and unterminated mode string
• Too few bytes
• Too many bytes

WRQ

• Mismatched opcode
• Missing filename
• Unterminated filename
• Missing mode string
• Unterminated mode string
• Unterminated filename and unterminated mode string
• Too few bytes
• Too many bytes

DATA

• Mismatched opcode
• No data
• Too few bytes
• Too many bytes

ACK

• Mismatched opcode
• Too few bytes
• Too many bytes

ERROR

• Mismatched opcode
• Missing error message
• Unterminated error message
• Too few bytes
• Too many bytes

Implement server-side connection initiation

Implement the server-side connection initiation protocol.