Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
asn1c
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
asn1c
Commits
79cb4c04
Commit
79cb4c04
authored
Mar 07, 2006
by
Lev Walkin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
*** empty log message ***
parent
e5d89ca6
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
7 deletions
+6
-7
asn1c/enber.1
asn1c/enber.1
+4
-5
asn1c/unber.1
asn1c/unber.1
+2
-2
No files found.
asn1c/enber.1
View file @
79cb4c04
...
...
@@ -14,16 +14,15 @@ enber \- Convert the unber XML output back into BER
.SH SYNOPSIS
enber [\fB-n\fR] [\fB-\fR] [\fIinfile\fR...]
.SH DESCRIPTION
enber takes the XML-formatted files produced by \fIunber\fR\|(1) and converts
them back into the BER format.
A single dash represents the standard input.
enber convers the XML-formatted files produced by \fIunber\fR\|(1) back into the BER format.
A single dash denotes the standard input.
.SH OPTIONS
.TP
\fB\-n\fR
Disable input validation. By default, enber performs some basic validity checks
against the XML input.
This option disables such checks.
against the XML input.
.SH EXAMPLES
Decode
the
BER sequence and immediately encode it back
Decode
a
BER sequence and immediately encode it back
.Vb
\& unber \fB-p\fR \fIfilename.ber\fR | enber \fB-\fR > \fIreconstructed.ber\fR
.Ve
...
...
asn1c/unber.1
View file @
79cb4c04
...
...
@@ -105,9 +105,9 @@ The constructed XML output is not necessarily well-formed.
When indefinite length encoding is being used, the BER sequence, which is not
terminated with the end-of-content octets, will cause the terminating \fB</I>\fR
XML tag to disappear.
Thus,
the
invalid BER framing directly causes invalid XML output.
Thus, invalid BER framing directly causes invalid XML output.
.P
The \&\fIenber\fR\|(1) utility understands
this convention
correctly.
The \&\fIenber\fR\|(1) utility understands
such XML
correctly.
.SH SEE ALSO
.TP
\&\fIenber\fR\|(1), \&\fIasn1c\fR\|(1)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment