-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathviathinksoft-std-0004-mcf1.nroff
299 lines (251 loc) · 8.51 KB
/
viathinksoft-std-0004-mcf1.nroff
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
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
.\" This document was created using "Nroff Internet Draft Editor"
.\" Note that a hotfix is required to use this program after 1st January 2020:
.\" https://misc.daniel-marschall.de/patches/nroffedit/
.\"
.\" Alternative, you can compile this document on Linux, using the following command:
.\" nroff -T ascii -ms viathinksoft-std-0004-mcf1.nroff | ./fix_formfeed.pl > viathinksoft-std-0004-mcf1.txt
.\" Note that "-ms" only works if the package "groff" is installed.
.\" fix.pl needs to be executed to replace FORMFEED.
.\" Note that the Linux command does not auto-generate the Table of Contents, since this is a NroffEdit feature!
.\"
.\" Note about section titles: According to RFC7322, the section capitalization should be Chicago Manual of Style
.\" Use this tool: https://titlecaseconverter.com/
.\"
.\" These values are required for my Debian Linux system (nroff) so that it outputs the same lines like NroffEdit
.pl 95n
.nr HM 6n
.nr FM 8n
.\" Page length
.\".pl 10.0i
.\" Page offset
.po 0
.\" Length of line
.ll 7.2i
.\" Length of title
.lt 7.2i
.\" Line Length (ms macro)
.nr LL 7.2i
.\" Title line length
.nr LT 7.2i
.\" Left footer text
.ds LF Marschall
.\" Right footer text. "FORMFEED" will be replaced by a post-processing script.
.ds RF FORMFEED[Page %]
.\" Left header text
.ds LH VTS/WF STD. 4
.\" Right header text
.ds RH 3 September 2024
.\" Center header text
.ds CH ViaThinkSoft MCF1
.\" Center footer text
.ds CF
.\" Hyphenation mode set to 0
.hy 0
.\" Disable hyphenation
.nh
.\" Adjust text left
.ad l
.\" Set indent (can be overridden for a single line using .ti = temporary indent)
.in 0
.nf
.tl 'VIATHINKSOFT/WEBFAN''D. Marschall'
.tl 'SPECIFICATION No. 4''ViaThinkSoft'
.tl 'First Draft: 2023''3 September 2024'
.fi
.\" Note. The ".tl" directive is used to generate the leading header
.\" in Internet drafts. The information specified after ".tl" provides
.\" left, center and right components of a line separated by the ' character
.\" in the following manner:
.\"
.\" .tl '<left component>'<center component>'<right component>'
.\"
.\" Only the left and right components are used in Internet-draft headers
.\" This and other comments in this template can safely be deleted.
.ce 3
=== ViaThinkSoft Modular Crypt Format 1.0 (MCF1) ===
.fi
.in 3
.ti 0
Abstract
This document describes how the standards for ViaThinkSoft and Webfan are defined, written, and published.
.ti 0
Identification of this Document
.in 3
.nf
Revision: 2024-09-03
State: In Force
Filename: viathinksoft-std-0004-mcf1.txt
URN: urn:x-viathinksoft:std:0004:2024-09-03
OID: 1.3.6.1.4.1.37476.3.0.1.1
{ iso(1) identified-organization(3) dod(6) internet(1)
private(4) enterprise(1) 37476 specifications(3)
misc(0) modular-crypt-format(1) vts-crypt-v1(1) }
WEID: weid:pen:SX0-3-0-1-1-5
IETF/RFC: (None)
.fi
.ti 0
Attachments
Reference implementation in PHP:
https://github.com/danielmarschall/php_utils/blob/master/\\
vts_crypt.inc.php
.ti 0
Copyright Notice
Copyright (c) 2023-2024 ViaThinkSoft and the persons identified as the
document authors. All rights reserved.
Licensed under the terms of the Apache 2.0 License.
.br
.\" These values are required for my Debian Linux system (nroff) so that it outputs the same lines like NroffEdit
.nr HM 8n
.nr FM 8n
.bp
.pl 96n
.\" \# TD4 -- Set TOC depth by altering this value (TD5 = depth 5)
.\" \# TOC -- Beginning of auto updated Table of Contents
.in 0
Table of Contents
.nf
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2 MCF Structure . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Test Vectors . . . . . . . . . . . . . . . . . . . . . . . . . 4
4 Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5 RA Considerations . . . . . . . . . . . . . . . . . . . . . . . 5
6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1 Normative References . . . . . . . . . . . . . . . . . . . 5
6.2 Informative References . . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
.fi
.in 3
.\" \# ETC -- End of auto updated Table of Contents
.bp
.ti 0
1 Introduction
ViaThinkSoft Modular Crypt Format 1.0 performs a simple hash or HMAC operation and stores the result in a Modular Crypt Format compatible string. No key derivation function or iterations are performed.
ViaThinkSoft MCF was invented to allow old passwords (e.g. MD5 with salt) to be easily converted to a MCF notation ($...$...$) so that these old passwords can be stored
in the same data structure as newer crypt passwords, until they get upgraded to a newer
hash. But it can also be used to encapsulate modern hash algorithms like SHA3/512 into
a MCF format, so that they can be stored together with other MCF passwords such as bcrypt.
Another innovation is to use Object Identifiers (OIDs) as MCF algorithm identifier.
Algorithm identifiers such as $1$, $2$, ... are nice to remember and short, but
can quickly lead to conflicts, and soon you run out of short identifiers.
.ti 0
1.1 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP\014 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
.ti 0
2 MCF Structure
Format of VTS MCF1:
.nf
$<id>$<params>$<salt>$<hash>
.fi
<id> is 1.3.6.1.4.1.37476.3.0.1.1
<params> is a=<algo>,m=<mode>[,i=<iterations>]
where <algo> is any valid hash algorithm (name scheme of PHP hash_algos() preferred), e.g.
.nf
- sha3-512
- sha3-384
- sha3-256
- sha3-224
- sha512
- sha512/256
- sha512/224
- sha384
- sha256
- sha224
- sha1
- md5
.fi
Not possible with MCF1 are these hashes (because they have a special salt-handling and output their own crypt format):
.nf
- bcrypt [Standardized crypt identifier 2, 2a, 2x, 2y]
- argon2i [Crypt identifier argon2i, not standardized]
- argon2id [Crypt identifier argon2i, not standardized]
.fi
Valid <mode> parameters:
.nf
- sp = salt + password
- ps = password + salt
- sps = salt + password + salt
- shp = salt + Hash(password)
- hps = Hash(password) + salt
- shps = salt + Hash(password) + salt
- hmac = HMAC (salt is the key)
- pbkdf2 = PBKDF2-HMAC
.fi
<iterations> can be omitted if 0. It is required for mode m=pbkdf2. For sp/ps/sps/shp/hps/shps/hmac, it is optional.
Like most Crypt-hashes, <salt> and <hash> are Radix64 coded
without padding and with alphabet
'./0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz'.
.ti 0
3 Test Vectors
Input: Hello World
.br
Hash: $1.3.6.1.4.1.37476.3.0.1.1$a=sha3-256,m=sp$$2Ud0hUTh//swVxoilAltWQ/9LQ189eZcdJ/hA5HkV/C
.br
Algorithm: SHA3-256
.br
Mode: sp (Salt || Password)
.br
Salt: None
Input: Hello World
.br
Hash: $1.3.6.1.4.1.37476.3.0.1.1$a=sha3-256,m=sp$CAT/9cvgCuS$dqNf5hJf0p09lYx.9rvI/c96swTz58tGhipuhobl8Ke
.br
Algorithm: SHA3-256
.br
Mode: sp (Salt || Password)
.br
Salt: 8 Bytes
.br
.br
.ti 0
4 Security Considerations
Hash values play a crucial role in various security contexts, such as password verification. For detailed guidance on securely managing hashes, please consult the relevant literature or documentation.
.bp
.ti 0
5 RA Considerations
.nf
OID: 1.3.6.1.4.1.37476.3.0.1.1
ASN1: { iso(1) identified-organization(3) dod(6) internet(1)
private(4) enterprise(1) 37476 specifications(3)
misc(0) modular-crypt-format(1) vts-crypt-v1(1) }
IRI: /.../Specifications/Misc/ModularCryptFormat/VtsCryptV1
WEID: weid:pen:SX0-3-0-1-1-5
.fi
.ti 0
6 References
.ti 0
6.1 Normative References
.in 14
.\" https://www.rfc-editor.org/refs/ref2119.txt
.ti 3
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP\014, RFC\02119, DOI\010.17487/RFC2119, March\01997,
.br
<https://www.rfc-editor.org/info/rfc2119>.
.in 3
.ti 0
6.2 Informative References
.in 14
.ti 3
None
.in 3
.ti 0
Acknowledgements
.in 3
I would like to thank Melanie Wehowski for her long time support in OIDplus and WEID projects.
This document was written in Nroff Internet Draft Editor by 3xA Security.
.br
https://aaa-sec.com/nroffedit/
.br
https://misc.daniel-marschall.de/patches/nroffedit/ ("year 2020" patch)
.ti 0
Authors' Addresses
.in 3
.nf
Daniel Marschall
Postfach 11 53
69243 Bammental
Germany
Email: [email protected]
URI: https://www.viathinksoft.com/
.fi