-
Notifications
You must be signed in to change notification settings - Fork 63
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Extract CBOR vars & funcs to new file cbor.go
- Loading branch information
Showing
5 changed files
with
157 additions
and
146 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,139 @@ | ||
| // Copyright (c) Faye Amacker. All rights reserved. | ||
| // Licensed under the MIT License. See LICENSE in the project root for license information. | ||
|
|
||
| package cbor | ||
|
|
||
| import ( | ||
| "errors" | ||
| "strconv" | ||
| ) | ||
|
|
||
| type cborType uint8 | ||
|
|
||
| const ( | ||
| cborTypePositiveInt cborType = 0x00 | ||
| cborTypeNegativeInt cborType = 0x20 | ||
| cborTypeByteString cborType = 0x40 | ||
| cborTypeTextString cborType = 0x60 | ||
| cborTypeArray cborType = 0x80 | ||
| cborTypeMap cborType = 0xa0 | ||
| cborTypeTag cborType = 0xc0 | ||
| cborTypePrimitives cborType = 0xe0 | ||
| ) | ||
|
|
||
| func (t cborType) String() string { | ||
| switch t { | ||
| case cborTypePositiveInt: | ||
| return "positive integer" | ||
| case cborTypeNegativeInt: | ||
| return "negative integer" | ||
| case cborTypeByteString: | ||
| return "byte string" | ||
| case cborTypeTextString: | ||
| return "UTF-8 text string" | ||
| case cborTypeArray: | ||
| return "array" | ||
| case cborTypeMap: | ||
| return "map" | ||
| case cborTypeTag: | ||
| return "tag" | ||
| case cborTypePrimitives: | ||
| return "primitives" | ||
| default: | ||
| return "Invalid type " + strconv.Itoa(int(t)) | ||
| } | ||
| } | ||
|
|
||
| type additionalInformation uint8 | ||
|
|
||
| const ( | ||
| maxAdditionalInformationWithoutArgument = 23 | ||
| additionalInformationWith1ByteArgument = 24 | ||
| additionalInformationWith2ByteArgument = 25 | ||
| additionalInformationWith4ByteArgument = 26 | ||
| additionalInformationWith8ByteArgument = 27 | ||
| additionalInformationAsIndefiniteLengthFlag = 31 | ||
| ) | ||
|
|
||
| func (ai additionalInformation) isIndefiniteLength() bool { | ||
| return ai == additionalInformationAsIndefiniteLengthFlag | ||
| } | ||
|
|
||
| const ( | ||
| // From RFC 8949.3: | ||
| // The initial byte of each encoded data item contains both information about the major type | ||
| // (the high-order 3 bits, described in Section 3.1) and additional information | ||
| // (the low-order 5 bits). | ||
|
|
||
| // typeMask is used to extract major type in initial byte of encoded data item. | ||
| typeMask = 0xe0 | ||
|
|
||
| // additionalInformationMask is used to extract additional information in initial byte of encoded data item. | ||
| additionalInformationMask = 0x1f | ||
| ) | ||
|
|
||
| func getType(raw byte) cborType { | ||
| return cborType(raw & typeMask) | ||
| } | ||
|
|
||
| func getAdditionalInformation(raw byte) byte { | ||
| return raw & additionalInformationMask | ||
| } | ||
|
|
||
| func isBreakFlag(raw byte) bool { | ||
| return raw == cborBreakFlag | ||
| } | ||
|
|
||
| func parseInitialByte(b byte) (t cborType, ai byte) { | ||
| return getType(b), getAdditionalInformation(b) | ||
| } | ||
|
|
||
| const ( | ||
| tagNumSelfDescribedCBOR = 55799 | ||
| tagNumExpectedLaterEncodingBase64URL = 21 | ||
| tagNumExpectedLaterEncodingBase64 = 22 | ||
| tagNumExpectedLaterEncodingBase16 = 23 | ||
| ) | ||
|
|
||
| var ( | ||
| cborBreakFlag = byte(0xff) | ||
| cborFalse = []byte{0xf4} | ||
| cborTrue = []byte{0xf5} | ||
| cborNil = []byte{0xf6} | ||
| cborNaN = []byte{0xf9, 0x7e, 0x00} | ||
| cborPositiveInfinity = []byte{0xf9, 0x7c, 0x00} | ||
| cborNegativeInfinity = []byte{0xf9, 0xfc, 0x00} | ||
| ) | ||
|
|
||
| // validBuiltinTag checks that supported built-in tag numbers are followed by expected content types. | ||
| func validBuiltinTag(tagNum uint64, contentHead byte) error { | ||
| t := getType(contentHead) | ||
| switch tagNum { | ||
| case 0: | ||
| // Tag content (date/time text string in RFC 3339 format) must be string type. | ||
| if t != cborTypeTextString { | ||
| return errors.New("cbor: tag number 0 must be followed by text string, got " + t.String()) | ||
| } | ||
| return nil | ||
| case 1: | ||
| // Tag content (epoch date/time) must be uint, int, or float type. | ||
| if t != cborTypePositiveInt && t != cborTypeNegativeInt && (contentHead < 0xf9 || contentHead > 0xfb) { | ||
| return errors.New("cbor: tag number 1 must be followed by integer or floating-point number, got " + t.String()) | ||
| } | ||
| return nil | ||
| case 2, 3: | ||
| // Tag content (bignum) must be byte type. | ||
| if t != cborTypeByteString { | ||
| return errors.New("cbor: tag number 2 or 3 must be followed by byte string, got " + t.String()) | ||
| } | ||
| return nil | ||
| case tagNumExpectedLaterEncodingBase64URL, tagNumExpectedLaterEncodingBase64, tagNumExpectedLaterEncodingBase16: | ||
| // From RFC 8949 3.4.5.2: | ||
| // The data item tagged can be a byte string or any other data item. In the latter | ||
| // case, the tag applies to all of the byte string data items contained in the data | ||
| // item, except for those contained in a nested data item tagged with an expected | ||
| // conversion. | ||
| return nil | ||
| } | ||
| return nil | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.