-
Notifications
You must be signed in to change notification settings - Fork 55
Expand file tree
/
Copy pathlib.rs
More file actions
249 lines (239 loc) · 7.89 KB
/
lib.rs
File metadata and controls
249 lines (239 loc) · 7.89 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
#![no_std]
#![cfg_attr(docsrs, feature(doc_auto_cfg))]
#![doc = include_str!("../README.md")]
#![doc(
html_logo_url = "https://raw.githubusercontent.com/RustCrypto/media/6ee8e381/logo.svg",
html_favicon_url = "https://raw.githubusercontent.com/RustCrypto/media/6ee8e381/logo.svg"
)]
#![forbid(unsafe_code)]
#![warn(
clippy::alloc_instead_of_core,
clippy::arithmetic_side_effects,
clippy::mod_module_files,
clippy::panic,
clippy::panic_in_result_fn,
clippy::std_instead_of_alloc,
clippy::std_instead_of_core,
clippy::unwrap_used,
missing_docs,
rust_2018_idioms,
unused_lifetimes,
unused_qualifications
)]
//! ## Conventions used in this crate
//!
//! This crate uses the following type labels which are described in
//! [RFC4251 § 5]:
//!
//! #### `byte`, `byte[n]`, `byte[]`
//!
//! A byte represents an arbitrary 8-bit value (octet).
//!
//! Fixed length data is sometimes represented as an array of bytes, written
//! `byte[n]` where `n` is the number of bytes in the array.
//!
//! `byte[]` is a newer convention from OpenSSH for describing arbitrary
//! length bytestrings (similar to `string`, see below) but identifies data
//! which is inherently binary in nature, as opposed to text.
//!
//! #### `boolean`
//!
//! A boolean value is stored as a single byte.
//!
//! The value 0 represents FALSE, and the value 1 represents TRUE. All non-zero
//! values MUST be interpreted as TRUE; however, applications MUST NOT
//! store values other than 0 and 1.
//!
//! #### `uint32`
//!
//! Represents a 32-bit unsigned integer.
//!
//! Stored as four bytes in the order of decreasing significance (network byte order).
//!
//! For example: the value `699921578` (`0x29b7f4aa`) is stored as
//! `29 b7 f4 aa`.
//!
//! #### `uint64`
//!
//! Represents a 64-bit unsigned integer.
//!
//! Stored as eight bytes in the order of decreasing significance (network byte order).
//!
//! #### `string`
//!
//! Arbitrary length binary string.
//!
//! Strings are allowed to contain arbitrary binary data, including null characters and 8-bit
//! characters.
//!
//! They are stored as a `uint32` containing its length
//! (number of bytes that follow) and zero (= empty string) or more
//! bytes that are the value of the string. Terminating null
//! characters are not used.
//!
//! Strings are also used to store text. In that case, US-ASCII is
//! used for internal names, and ISO-10646 UTF-8 for text that might
//! be displayed to the user. The terminating null character SHOULD
//! NOT normally be stored in the string. For example: the US-ASCII
//! string "testing" is represented as `00 00 00 07 t e s t i n g`. The
//! UTF-8 mapping does not alter the encoding of US-ASCII characters.
//!
//! #### `mpint`
//!
//! Represents multiple precision integers in two's complement format,
//! stored as a string, 8 bits per byte, MSB first.
//!
//! Negative numbers have the value 1 as the most significant bit of the first byte of
//! the data partition. If the most significant bit would be set for
//! a positive number, the number MUST be preceded by a zero byte.
//! Unnecessary leading bytes with the value 0 or 255 MUST NOT be
//! included. The value zero MUST be stored as a string with zero
//! bytes of data.
//!
//! By convention, a number that is used in modular computations in
//! `Z_n` SHOULD be represented in the range `0 <= x < n`.
//!
//! Examples:
//!
//! value (hex) | representation (hex)
//! -------------------|---------------------
//! `0` | `00 00 00 00`
//! `9a378f9b2e332a7` | `00 00 00 08 09 a3 78 f9 b2 e3 32 a7`
//! `80` | `00 00 00 02 00 80`
//! `-1234` | `00 00 00 02 ed cc`
//! `-deadbeef` | `00 00 00 05 ff 21 52 41 11`
//!
//! #### `name-list`
//!
//! A string containing a comma-separated list of names.
//!
//! A `name-list` is represented as a `uint32` containing its length
//! (number of bytes that follow) followed by a comma-separated list of zero or more
//! names. A name MUST have a non-zero length, and it MUST NOT
//! contain a comma (",").
//!
//! As this is a list of names, all the elements contained are names and MUST be in US-ASCII.
//!
//! Context may impose additional restrictions on the names. For example,
//! the names in a name-list may have to be a list of valid algorithm
//! identifiers (see Section 6 below), or a list of [RFC3066] language
//! tags. The order of the names in a name-list may or may not be
//! significant. Again, this depends on the context in which the list
//! is used.
//!
//! Terminating null characters MUST NOT be used, neither
//! for the individual names, nor for the list as a whole.
//!
//! Examples:
//!
//! value | representation (hex)
//! ---------------------------|---------------------
//! `()`, the empty name-list | `00 00 00 00`
//! `("zlib")` | `00 00 00 04 7a 6c 69 62`
//! `("zlib,none")` | `00 00 00 09 7a 6c 69 62 2c 6e 6f 6e 65`
//!
//! [RFC3066]: https://datatracker.ietf.org/doc/html/rfc3066
//! [RFC4251 § 5]: https://datatracker.ietf.org/doc/html/rfc4251#section-5
//!
//! ## Deriving [`Decode`] and [`Encode`]
//!
//! The traits [`Decode`] and [`Encode`] can be derived for any struct or enum where all its fields
//! implement [`Decode`] and [`Encode`] respectively.
//!
//! To use this functionality, enable the `derive` crate feature for `ssh-encoding`.
//!
//! ### Example
//!
//! Here is an example of how you could define a handful of the SSH message types:
//!
#![cfg_attr(all(feature = "alloc", feature = "derive"), doc = "```")]
#![cfg_attr(not(all(feature = "alloc", feature = "derive")), doc = "```ignore")]
//! use ssh_encoding::{Decode, Encode};
//!
//! #[derive(Debug, PartialEq, Encode, Decode)]
//! #[repr(u8)]
//! enum Message {
//! Disconnect {
//! reason_code: u32,
//! description: String,
//! language_tag: String,
//! } = 1,
//! EcdhInit {
//! client_public_key: Vec<u8>,
//! } = 30,
//! EcdhReply {
//! host_key: HostKey,
//! server_public_key: Vec<u8>,
//! #[ssh(length_prefixed)]
//! host_signature: HostSignature,
//! } = 31,
//! }
//!
//! #[derive(Debug, PartialEq, Encode, Decode)]
//! #[ssh(length_prefixed)]
//! struct HostKey {
//! key_type: String,
//! ecdsa_curve_identifier: String,
//! ecdsa_public_key: Vec<u8>,
//! }
//!
//! #[derive(Debug, PartialEq, Encode, Decode)]
//! struct HostSignature {
//! signature_type: String,
//! signature: Vec<u8>,
//! }
//!
//! let message = Message::EcdhReply {
//! host_key: HostKey {
//! key_type: "ecdsa-sha2-nistp256".into(),
//! ecdsa_curve_identifier: "nistp256".into(),
//! ecdsa_public_key: vec![0x01, 0x02, 0x03],
//! },
//! server_public_key: vec![0x04, 0x05, 0x06],
//! host_signature: HostSignature {
//! signature_type: "ecdsa-sha2-nistp256".into(),
//! signature: vec![0x07, 0x08, 0x09],
//! },
//! };
//!
//! let encoded = message.encode_vec().unwrap();
//! assert_eq!(&encoded[..13], &[31, 0, 0, 0, 42, 0, 0, 0, 19, 101, 99, 100, 115]);
//! let decoded = Message::decode(&mut &encoded[..]).unwrap();
//! assert_eq!(message, decoded);
//! ```
#[cfg(feature = "alloc")]
#[macro_use]
extern crate alloc;
mod checked;
mod decode;
mod encode;
mod error;
mod label;
#[macro_use]
mod reader;
mod writer;
#[cfg(feature = "base64")]
pub mod base64;
#[cfg(feature = "pem")]
pub mod pem;
pub use crate::{
checked::CheckedSum,
decode::Decode,
encode::Encode,
error::{Error, Result},
label::{Label, LabelError},
reader::Reader,
writer::Writer,
};
#[cfg(feature = "base64")]
pub use crate::{base64::Base64Reader, base64::Base64Writer};
#[cfg(feature = "bytes")]
pub use bytes;
#[cfg(feature = "digest")]
pub use crate::writer::DigestWriter;
#[cfg(feature = "digest")]
pub use digest;
#[cfg(feature = "pem")]
pub use crate::pem::{DecodePem, EncodePem};
#[cfg(feature = "derive")]
pub use ssh_derive::{Decode, Encode};