asn1c:ASN.1到C编译器，支持多种编码格式的序列化与反序列化

The ASN.1 Compiler

文件	最后提交记录	最后更新时间
asn1-tools	fix the rest of type conversions for printing	7 年前
asn1c	Reject -fno-constraints together with -gen-PER/-gen-OER PER and OER derive the wire encoding from the type constraints (SIZE and value ranges select the packed representation), so generating those codecs with constraint checking disabled would silently emit non-conformant output. Previously the combination also failed to compile, because the member tables referenced the per-member OER/PER constraint descriptors that -fno-constraints omits. Refuse the combination at option-validation time with a clear diagnostic. Since PER and OER are enabled by default, -fno-constraints must be paired with -no-gen-PER -no-gen-OER (i.e. used only for BER/DER/XER, where constraints are validation-only).	2 个月前
doc	Refresh publication year	2 个月前
examples	Fix usage cmd in README of examples/sample.source.LDAP3	6 年前
libasn1common	add stdarg	7 年前
libasn1compiler	Fix open type decoder NULL deref and OOB access on typeless IOS rows When an information object set leaves the open type's class field unspecified for some objects (an OPTIONAL &Type field omitted by part of the set, as in 3GPP elementary-procedure tables), the open type CHOICE only contains the rows that actually define a type, but the generated type selector returned the raw information object set row number as the presence index. Two defects followed, both reachable from untrusted decoder input (BER/OER/PER/XER): * A value whose discriminant selects a typeless row made the selector hand back a NULL type descriptor with a non-zero presence index; the decoders only checked the presence index and then dereferenced the NULL descriptor. * A value selecting a later, defined row indexed past the CHOICE elements array. The out-of-bounds member offset is then used as the address the inner value is decoded into, turning the read into an out-of-bounds write of attacker-influenced data. Fixes: * libasn1compiler: the generated selector now counts only the rows that define a type to derive the presence index, and leaves the result cleared for a typeless row. For gap-free object sets this is identical to the previous row+1, so existing output is unchanged in behaviour. * skeletons (OPEN_TYPE ber/xer/uper and oer getters): also reject a selection with a NULL type descriptor, protecting code generated by older compilers when linked against the updated skeletons. Adds regression test 161 (valid message round-trips; typeless discriminant fails cleanly) and regenerates the affected IOS reference outputs (139/140/141/144/146/156). Reported by Seaver Thorn (NCSU).	2 个月前
libasn1fix	fix library dependency management	8 年前
libasn1parser	Fix CVE-2025-32893: compare constraints in asn1p_expr_compare() asn1p_expr_compare() never compared the `constraints` field, and asn1p_constraint_compare() was an unimplemented stub that aborted. As a result two parameterized expressions differing only by their VALUESET constraint were treated as identical, so asn1f_parameterization_fork() did not fork them. The second usage of a parameterized type silently reused the first value set's information object table, producing incomplete validation code (any input accepted) -- CWE-1287/CWE-183, remote, data-integrity. Implement asn1p_constraint_compare() (distinguishing VALUESET references) and consult it from asn1p_expr_compare(), so distinct value sets produce distinct, complete information object tables. Hardened relative to the upstream one-liner: a constraint_ref() helper guards every intermediate NULL pointer and the reference comp_count, so the comparison never NULL-derefs or asserts on constraint shapes other than the VALUESET-reference case, while keeping the intended semantics identical. Ported from velichkov/asn1c commit aa8c06f9e54975034abc88464e701373985bbc45. New regression test tests/tests-asn1c-compiler/163-ios-valueset-fork-OK: two information object sets differing only by their value sets, each used to parameterize the same type. Before the fix the second usage collapses onto the first set's table (229-line diff vs golden); after the fix the two usages fork into distinct, complete types (SetA -> _P0, SetB -> _P1).	2 个月前
libasn1print	removed gcc-7 warnings	8 年前
m4	add options to readme	8 年前
skeletons	Fix NULL deref in open type decode failure-cleanup path When the inner decode of an open type value failed (RC_FAIL/RC_WMORE) and the open type member is inline, the cleanup reset the member with memset(memb_ptr2, 0, selected.type_descriptor->specifics->struct_size) i.e. it used the selected variant's* specifics to size a reset of the open type CHOICE structure. For a variant whose descriptor has no asn_CHOICE_specifics (e.g. a primitive such as BOOLEAN) that pointer is NULL, so sizing the memset dereferenced NULL; for other variants it used the wrong structure size. Use the open type's own CHOICE specifics (elm->type->specifics) instead, in the BER, XER, uPER and OER getters. Reachable from untrusted input on the same constructs as the preceding open type fixes. Found by a libFuzzer harness over the open type decoders (tests-c-compiler/check-src/check-162.c).	2 个月前
tests	tests: add runtime behavioral test for CVE-2025-32893 (check-164) The existing 163 test only diffs the generated source; it cannot run because asn1c emits non-compilable C for value sets that bind an inline built-in type to &Type. This adds a compilable companion spec (164) whose two object sets bind the SAME &id (1) to DIFFERENT named types (IntPayload INTEGER vs StrPayload IA5String), and a check-program that compiles the spec and runs the generated decoder: * an IA5String payload at id 1 (valid under SetB, which parameterizes `second') must be accepted; * an INTEGER payload at id 1 (valid only under SetA) must be rejected. Without the fix, asn1f_parameterization_fork() does not fork the two parameterizations, `second' reuses SetA's table, and both assertions flip (INTEGER accepted, IA5String rejected) -- so the test aborts. Verified against an unpatched build (007e3b6b): check-164 fails with the IA5String value rejected (code 2); with the fix it passes. Full `make check` green under a default ./configure.	2 个月前
.clang-format	clang-format config with my preferred style	10 年前
.gitignore	[unber] fix buffer overrun in the BER introspection and debugging tool (unber)	7 年前
.travis.yml	allow fully default flags for distcheck	8 年前
AUTHORS	Add Jie Chen to AUTHORS	2 个月前
BUGS	BIT STRING identifiers is not a problem	21 年前
ChangeLog	Fix CVE-2025-32893: compare constraints in asn1p_expr_compare() asn1p_expr_compare() never compared the `constraints` field, and asn1p_constraint_compare() was an unimplemented stub that aborted. As a result two parameterized expressions differing only by their VALUESET constraint were treated as identical, so asn1f_parameterization_fork() did not fork them. The second usage of a parameterized type silently reused the first value set's information object table, producing incomplete validation code (any input accepted) -- CWE-1287/CWE-183, remote, data-integrity. Implement asn1p_constraint_compare() (distinguishing VALUESET references) and consult it from asn1p_expr_compare(), so distinct value sets produce distinct, complete information object tables. Hardened relative to the upstream one-liner: a constraint_ref() helper guards every intermediate NULL pointer and the reference comp_count, so the comparison never NULL-derefs or asserts on constraint shapes other than the VALUESET-reference case, while keeping the intended semantics identical. Ported from velichkov/asn1c commit aa8c06f9e54975034abc88464e701373985bbc45. New regression test tests/tests-asn1c-compiler/163-ios-valueset-fork-OK: two information object sets differing only by their value sets, each used to parameterize the same type. Before the fix the second usage collapses onto the first set's table (229-line diff vs golden); after the fix the two usages fork into distinct, complete types (SetA -> _P0, SetB -> _P1).	2 个月前
FAQ	comments added to highlight transfer syntax compatibility	8 年前
INSTALL.md	add options to readme	8 年前
LICENSE	copyright info	9 年前
Makefile.am	moved unber and enber into asn1-tools	7 年前
README.md	lang fixes	8 年前
REQUIREMENTS.md	recommend 64-bit	8 年前
SECURITY.md	Add SECURITY.md with vulnerability disclosure policy Documents the two security surfaces (compiler vs generated code/skeletons), reporting process, and response timeline.	3 个月前
configure.ac	configure.ac: don't fail when cross-compiling ASan leak probe AC_RUN_IFELSE executes a test binary to check whether the AddressSanitizer runtime supports leak detection. Without an action-if-cross-compiling branch, this aborts configure entirely under cross-compilation instead of degrading gracefully, since the resulting binary cannot run on the build host. Add a cross-compiling fallback that warns and leaves ASAN_ENV_FLAGS unset, matching the pessimistic-default approach autoconf recommends for runtime checks and the soft-fail pattern already used elsewhere in this file for unsupported sanitizer features.	2 个月前

自动翻译

关于

ASN.1到C编译器接收ASN.1模块文件（例如），生成与C++兼容的C源代码。这些代码可以用来序列化本地C结构，将其转化为紧凑且无歧义的基于BER/OER/PER/XER的数据文件，以及反序列化回这些文件。

各种基于ASN.1的格式在行业中广泛应用，如用于HTTPS握手时编码X.509证书，手机和蜂窝网络之间交换控制数据，以及智能交通网络中实现车对车通信。

ASN.1标准族庞大而复杂，目前没有开源编译器能完全支持它。asn1c可能是最成熟的开放源码ASN.1编译器。

ASN.1传输语法

ASN.1编码互操作性表

ASN.1标准族定义了多种数据编码方式，包括字节导向型（如BER）、位导向型（如PER）和文本型（如XER）。某些编码变体（如DER）只是更通用编码（如BER）的严格版本。

以下互操作性表格指定了哪些API函数可用于以兼容方式交换数据。如果你需要根据第1列中的标准生产数据，使用第2列中的API函数。如果你需要处理符合第3列中指定的标准的数据，使用第4列中的API函数。详情参见doc/asn1c-usage.pdf。

编码	API 函数	可理解的编码	API 函数
BER	der_encode()	BER	ber_decode()
DER	der_encode()	DER, BER	ber_decode()
CER	不支持	CER, BER	ber_decode()
BASIC-OER	oer_encode()	*-OER	oer_decode()
CANONICAL-OER	oer_encode()	*-OER	oer_decode()
BASIC-UPER	uper_encode()	*-UPER	uper_decode()
CANONICAL-UPER	uper_encode()	*-UPER	uper_decode()
*-APER	不支持	*-APER	不支持
BASIC-XER	xer_encode(XER_F_BASIC)	*-XER	xer_decode()
CANONICAL-XER	xer_encode(XER_F_CANONICAL)	*-XER	xer_decode()