Question

I am going to be implementing a network protocol (specifically, SFTP) and I wondered if there are any general rules-of-thumb to follow?

At the moment it seems like a mammoth task and I’m at a loss as where to start.

I’m looking for:

• Tips
• Best practices
• Possible design patterns
• Experiences

Try to keep it applicable to network protocols in general.

Thanks!

Answer 1

I would certainly recommend using well tested libraries if possible. Especially for the SSH side of SFTP – as mistakes in implementation could lead to security vulnerabilities.

That said, you seem like an experienced person, and you may find that none of the libraries out there (SharpSSH etc.) are appropriate, you should consider seperating your network implementation out into its own library and open sourcing it for two reasons:

1. If it is useful to you, it may well be useful to someone else.
2. You might get some helpful code review

Given all that, other guidelines to follow would be similar to other developments, but perhaps with more rigour regarding security and testing. Making sure you run static analysis and that you unit test for failure cases.

Also: Use, but don’t trust the lower layers of the OSI model that are provided for you. If there is a scenario that breaks your code, you can bet that the network will find it eventually.

Hope this helps.