blob: 827c211b75875ddd70f80b8bed82aa004470db6e [file] [log] [blame]
Lev Walkinc6080fd2016-01-23 06:35:34 -08001.\" Automatically generated by Pandoc 1.16.0.2
2.\"
3.ad l
4.TH "enber" "1" "2016\-01\-23" "unber(1) counterpart" "Version 0.9.28"
5.nh \" Turn off hyphenation by default.
6.SH NAME
7.PP
8enber \-\- Convert the unber XML output back into BER
9.SH SYNOPSIS
10.PP
11enber [\f[B]\-n\f[]] [\f[B]\-\f[]] [\f[I]input\-filenames\f[]...]
12.SH DESCRIPTION
13.PP
14enber converts the XML\-formatted files produced by \f[C]unber\f[](1)
15back into the BER format.
16A single dash denotes the standard input.
17.SH OPTIONS
18.TP
19.B \-n
20Disable input validation.
21By default, enber performs some basic validity checks against XML input.
22.RS
23.RE
24.SH EXAMPLES
25.PP
26Decode a BER sequence and immediately encode it back
27.RS
28.PP
29unber \f[B]\-p\f[] \f[I]filename.ber\f[] | enber \f[B]\-\f[] >
30\f[I]reconstructed.ber\f[]
31.RE
32.SH FOOTNOTES
33.PP
34This program does not attempt to perform full\-fledged XML parsing.
35It is merely compatible with \f[C]unber\f[](1)\[aq]s output.
36In particular, the XML style comments are not supported.
37A hash "\f[B]#\f[]" or two dashes "\f[B]\-\-\f[]" following a whitespace
38is treated as a beginning of a comment line, which is ignored
39completely.
40Empty lines are ignored as well.
41.PP
42The following example \f[C]enber\f[](1) input demostrates the use of
43comments:
44.PP
45<C O="0" T="[1]" TL="2" V="2">
46.PD 0
47.P
48.PD
49\ \ \ \ <I O="2" T="[1]" TL="2" V="Indefinite">
50.PD 0
51.P
52.PD
53\ \ \ \ \f[B]\-\-\f[] </I O="4" T="[UNIVERSAL 0]" L="4">
54.PD 0
55.P
56.PD
57\ \ \ \ \f[B]#\f[] Do not terminate:
58.PD 0
59.P
60.PD
61\ \ \ \ \f[B]#\f[] the absence of end\-of\-content octets is
62intentional!
63.PD 0
64.P
65.PD
66</C O="6" T="[1]" L="6">
67.SH SEE ALSO
68.PP
69\f[C]unber\f[](1), \f[C]asn1c\f[](1).
70.SH AUTHORS
71Lev Walkin <vlm@lionet.info>.