Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2024-11-26 17:32
📁 .static	-	2024-11-26 17:32
📄 changelog.rst Changelog ========= .. include:: ../../CHANGES.rst	54 B	2024-11-26 17:32
📄 conf.py # -- coding: utf-8 -- # # PyASN1 documentation build configuration file, created by # sphinx-quickstart on Sat Jun 27 23:15:54 2015. # # This file is execfile()d with the current directory set to its # containing dir. # # Note that not all possible configuration values are present in this # autogenerated file. # # All configuration values have a default; values that are commented out # serve to show the default. # If extensions (or modules to document with autodoc) are in another directory, # add these directories to sys.path here. If the directory is relative to the # documentation root, use os.path.abspath to make it absolute, like shown here. # sys.path.insert(0, os.path.abspath('.')) import os, sys # add ../.. to module lookup path sys.path.insert( 0, os.path.abspath( os.path.join(os.path.dirname(__file__), "..", "..") ) ) import pyasn1 # -- General configuration ------------------------------------------------ # If your documentation needs a minimal Sphinx version, state it here. # needs_sphinx = '1.0' # Add any Sphinx extension module names here, as strings. They can be # extensions coming with Sphinx (named 'sphinx.ext.') or your custom # ones. extensions = [ 'sphinx.ext.autodoc', 'sphinx.ext.napoleon', 'sphinx.ext.intersphinx', ] # Add any paths that contain templates here, relative to this directory. templates_path = ['.templates'] # The suffix(es) of source filenames. # You can specify multiple suffix as a list of string: # source_suffix = ['.rst', '.md'] source_suffix = '.rst' # The encoding of source files. # source_encoding = 'utf-8-sig' # The master toctree document. master_doc = 'contents' # General information about the project. project = u'ASN.1 types and codecs' copyright = u'2005-2020, Ilya Etingof <etingof@gmail.com>' author = u'Ilya Etingof <etingof@gmail.com>' # The version info for the project you're documenting, acts as replacement for # \|version\| and \|release\|, also used in various other places throughout the # built documents. # # The short X.Y version. version = ".".join(pyasn1.__version__.split(".")[:2]) # The full version, including alpha/beta/rc tags. release = pyasn1.__version__ # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. # # This is also used if you do content translation via gettext catalogs. # Usually you set "language" from the command line for these cases. language = "en" # There are two options for replacing \|today\|: either, you set today to some # non-false value, then it is used: # today = '' # Else, today_fmt is used as the format for a strftime call. # today_fmt = '%B %d, %Y' # List of patterns, relative to source directory, that match files and # directories to ignore when looking for source files. exclude_patterns = [] # The reST default role (used for this markup: `text`) to use for all # documents. # default_role = None # If true, '()' will be appended to :func: etc. cross-reference text. # add_function_parentheses = True # If true, the current module name will be prepended to all description # unit titles (such as .. function::). # add_module_names = True # If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. # show_authors = False # The name of the Pygments (syntax highlighting) style to use. pygments_style = 'sphinx' # A list of ignored prefixes for module index sorting. # modindex_common_prefix = [] # If true, keep warnings as "system message" paragraphs in the built documents. # keep_warnings = False # If true, `todo` and `todoList` produce output, else they produce nothing. todo_include_todos = False # -- Options for HTML output ---------------------------------------------- # The theme to use for HTML and HTML Help pages. See the documentation for # a list of builtin themes. html_theme = 'alabaster' # Theme options are theme-specific and customize the look and feel of a theme # further. For a list of options available for each theme, see the # documentation. html_theme_options = { 'logo': 'logo.svg', 'description': '<p align=left><i><b>Brewing free software for the greater good</i></b></p>', 'show_powered_by': False, 'github_user': 'etingof', 'github_repo': 'pyasn1', 'fixed_sidebar': True, } html_sidebars = { '*': [ 'about.html', 'navigation.html', 'relations.html', 'searchbox.html', 'donate.html', ] } # Add any paths that contain custom themes here, relative to this directory. # html_theme_path = [] # The name for this set of Sphinx documents. If None, it defaults to # "<project> v<release> documentation". # html_title = None # A shorter title for the navigation bar. Default is the same as html_title. # html_short_title = None # The name of an image file (relative to this directory) to place at the top # of the sidebar. # html_logo = "" # The name of an image file (within the static path) to use as favicon of the # docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32 # pixels large. html_favicon = '.static/favicon.ico' # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". html_static_path = ['.static'] # Add any extra paths that contain custom files (such as robots.txt or # .htaccess) here, relative to this directory. These files are copied # directly to the root of the documentation. # html_extra_path = [] # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. # html_last_updated_fmt = '%b %d, %Y' # If true, SmartyPants will be used to convert quotes and dashes to # typographically correct entities. # html_use_smartypants = True # Custom sidebar templates, maps document names to template names. # html_sidebars = {} # Additional templates that should be rendered to pages, maps page names to # template names. # html_additional_pages = {} # If false, no module index is generated. # html_domain_indices = True # If false, no index is generated. # html_use_index = True # If true, the index is split into individual pages for each letter. # html_split_index = False # If true, links to the reST sources are added to the pages. html_show_sourcelink = False # If true, "Created using Sphinx" is shown in the HTML footer. Default is True. html_show_sphinx = False # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True. # html_show_copyright = True # If true, an OpenSearch description file will be output, and all pages will # contain a <link> tag referring to it. The value of this option must be the # base URL from which the finished HTML is served. # html_use_opensearch = '' # This is the file name suffix for HTML files (e.g. ".xhtml"). # html_file_suffix = None # Language to be used for generating the HTML full-text search index. # Sphinx supports the following languages: # 'da', 'de', 'en', 'es', 'fi', 'fr', 'hu', 'it', 'ja' # 'nl', 'no', 'pt', 'ro', 'ru', 'sv', 'tr' # html_search_language = 'en' # A dictionary with options for the search language support, empty by default. # Now only 'ja' uses this config value # html_search_options = {'type': 'default'} # The name of a javascript file (relative to the configuration directory) that # implements a search results scorer. If empty, the default will be used. # html_search_scorer = 'scorer.js' # Output file base name for HTML help builder. htmlhelp_basename = 'pyasn1doc' # html_context = { # 'include_analytics': 'PYASN1DEV' in os.environ # } # -- Options for LaTeX output --------------------------------------------- latex_elements = { # The paper size ('letterpaper' or 'a4paper'). # 'papersize': 'letterpaper', # The font size ('10pt', '11pt' or '12pt'). # 'pointsize': '10pt', # Additional stuff for the LaTeX preamble. # 'preamble': '', # Latex figure (float) alignment # 'figure_align': 'htbp', } # Grouping the document tree into LaTeX files. List of tuples # (source start file, target name, title, # author, documentclass [howto, manual, or own class]). latex_documents = [ (master_doc, 'PyASN1.tex', u'PyASN1 Documentation', u'Ilya Etingof \\textless{}etingof@gmail.com\\textgreater{}', 'manual'), ] # The name of an image file (relative to this directory) to place at the top of # the title page. # latex_logo = None # For "manual" documents, if this is true, then toplevel headings are parts, # not chapters. # latex_use_parts = False # If true, show page references after internal links. # latex_show_pagerefs = False # If true, show URL addresses after external links. # latex_show_urls = False # Documents to append as an appendix to all manuals. # latex_appendices = [] # If false, no module index is generated. # latex_domain_indices = True # -- Options for manual page output --------------------------------------- # One entry per manual page. List of tuples # (source start file, name, description, authors, manual section). man_pages = [ (master_doc, 'pyasn1', u'PyASN1 Documentation', [author], 1) ] # If true, show URL addresses after external links. # man_show_urls = False # -- Options for Texinfo output ------------------------------------------- # Grouping the document tree into Texinfo files. List of tuples # (source start file, target name, title, author, # dir menu entry, description, category) texinfo_documents = [ (master_doc, 'PyASN1', u'PyASN1 Documentation', author, 'PyASN1', 'One line description of project.', 'Miscellaneous'), ] # Documents to append as an appendix to all manuals. # texinfo_appendices = [] # If false, no module index is generated. # texinfo_domain_indices = True # How to display URL addresses: 'footnote', 'no', or 'inline'. # texinfo_show_urls = 'footnote' # If true, do not generate a @detailmenu in the "Top" node's menu. # texinfo_no_detailmenu = False # Example configuration for intersphinx: refer to the Python standard library. intersphinx_mapping = {'python': ('https://docs.python.org/3.10/', None)} # this merges constructor docstring with class docstring autoclass_content = 'both' # Sort members by type autodoc_member_order = 'bysource' # autodoc_member_order = 'groupwise' # Napoleon settings napoleon_google_docstring = False napoleon_numpy_docstring = True napoleon_include_private_with_doc = False napoleon_include_special_with_doc = True napoleon_use_admonition_for_examples = False napoleon_use_admonition_for_notes = False napoleon_use_admonition_for_references = False napoleon_use_ivar = False napoleon_use_param = False napoleon_use_rtype = False	10.57 KB	2024-11-26 17:32
📄 contents.rst .. _Start Content: ASN.1 library for Python ======================== .. toctree:: :maxdepth: 1 Abstract Syntax Notation One (`ASN.1 <http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_1x>`_) is a technology for exchanging structured data in a universally understood, hardware agnostic way. Many industrial, security and telephony applications heavily rely on ASN.1. The `pyasn1 <https://pypi.org/project/pyasn1/>`_ library implements ASN.1 support in pure-Python. What is ASN.1 ------------- ASN.1 is a large, arguably over-engineered and extremely old data modelling and serialisation tool. It is probably among the first serialisation protocols in the history of computer science and technology. ASN.1 started its life over 30 years ago as a serialisation mechanism for the first electronic mail (known as X.400). Later on if was split off the e-mail application and become a stand-alone tech still being actively supported by its designers and widely used in industry and technology. Since then ASN.1 is sort of haunted by its relations with the OSI model -- the first, unsuccessful, version of the Internet. You can read many interesting `discussions <https://news.ycombinator.com/item?id=8871453>`_ on that topic. In the following years, generations of software engineers tackled the serialisation problem many times. We can see that in Google's `ProtoBuffers <https://developers.google.com/protocol-buffers/>`_ or `FlatBuffers <https://google.github.io/flatbuffers/>`_, for example. Interestingly, many new takes on binary protocol design do not depart far from ASN.1 from technical perspective. It's more of a matter of striking a balance between processing overhead, wire format overhead and human readability. Looking at what ASN.1 has to offer, it has three loosely coupled parts: * Data types: the standard introduces a collection of basic data types (integers, bits, strings, arrays and records) that can be used for describing arbitrarily complex, nested data structures. * Serialisation protocols: the above data structures could be converted into a series of octets for storage or transmission over the wire as well as recovered back into their structured form. The system is fully agnostic to hardware architectures differences. * Schema language: ASN.1 data structures could be described in terms of a schema language for ASN.1 compiler to turn it into platform-specific implementation. ASN.1 applications ------------------ Being an old and generally successful standard, ASN.1 is widely adopted for many uses. To give you an example, these technologies use ASN.1 for their data exchange needs: * Signaling standards for the public switched telephone network (SS7 family) * Network management standards (SNMP, CMIP) * Directory standards (X.500 family, LDAP) * Public Key Infrastructure standards (X.509, etc.) * PBX control (CSTA) * IP-based Videoconferencing (H.323 family) * Biometrics (BIP, CBEFF, ACBio) * Intelligent transportation (SAE J2735) * Cellular telephony (GSM, GPRS/EDGE, UMTS, LTE) ASN.1 gotchas ------------- Apparently, ASN.1 is hard to implement properly. Quality open-source ASN.1 tools are rare, but ad-hoc implementations are numerous. Judging from the `statistics <http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ASN.1>`_ on discovered security vulnerabilities, many people have implemented ASN.1 parsers and oftentimes fell victim to its edge cases. On the bright side, ASN.1 has been around for a long time, it is well understood and security reviewed. Documentation ------------- .. toctree:: :maxdepth: 2 /pyasn1/contents Use case -------- .. toctree:: :maxdepth: 2 /example-use-case Download & Install ------------------ .. toctree:: :maxdepth: 2 /download Changes ------- All changes and release history is maintained in changelog. There you could also download the latest unreleased pyasn1 tarball containing the latest fixes and improvements. .. toctree:: :maxdepth: 1 /changelog License ------- The PyASN1 software is distributed under 2-clause BSD License. .. toctree:: :maxdepth: 2 /license Getting help ------------ Please, file your `issues <https://github.com/pyasn1/pyasn1/issues>`_ and `PRs <https://github.com/pyasn1/pyasn1/pulls>`_ at GitHub. Alternatively, you could ask for help at `Stack Overflow <http://stackoverflow.com/questions/tagged/pyasn1>`_ or search `pyasn1-users <https://lists.sourceforge.net/lists/listinfo/pyasn1-users>`_ mailing list archive. Books on ASN.1 -------------- The pyasn1 implementation is largely based on reading up the following awesome books: * `ASN.1 - Communication between heterogeneous systems <http://www.oss.com/asn1/dubuisson.html>`_ by Olivier Dubuisson * `ASN.1 Complete <http://www.oss.com/asn1/resources/books-whitepapers-pubs/larmouth-asn1-book.pdf>`_ by Prof John Larmouth Here you can get the official standards which is hard to read: * `ITU standards <http://www.itu.int/ITU-T/studygroups/com17/languages/X.680-X.693-0207w.zip>`_ On the other end of the readability spectrum, here is a quick and sweet write up: * `A Layman's Guide to a Subset of ASN.1, BER, and DER <https://www.researchgate.net/publication/2820226_A_Layman's_Guide_to_a_Subset_of_ASN1_BER_and_DER>`_ by Burton S. Kaliski If you are working with ASN.1, we'd highly recommend reading a proper book on the subject. .. hidden toctree to include `index.rst` for RTD .. toctree:: :hidden: /index	5.35 KB	2024-11-26 17:32
📄 download.rst Download & Install ================== The pyasn1 library is a pure-Python package with no external dependencies. It works with Python 3.8+. The best way to obtain PyASN1 is by running `pip`: .. code-block:: bash $ virtualenv venv $ source venv/bin/activate $ pip install pyasn1 You may also want to use `pyasn1-modules`: .. code-block:: bash $ pip install pyasn1-modules Alternatively, you can download the latest release from `GitHub <https://github.com/pyasn1/pyasn1/releases>`_ or `PyPI <https://pypi.org/project/pyasn1>`_.	550 B	2024-11-26 17:32
📄 example-use-case.rst Example use case ================ .. toctree:: :maxdepth: 2 To briefly explain how to approach pyasn1, consider a quick workflow example. Grab ASN.1 schema for SSH keys ------------------------------ ASN.1 is widely used in many Internet protocols. Frequently, whenever ASN.1 is employed, data structures are described in ASN.1 schema language right in the RFC. Take `RFC2437 <https://www.ietf.org/rfc/rfc2437.txt>`_ for example -- we can look into it and weed out data structures specification into a local file: .. code-block:: python # pkcs-1.asn PKCS-1 {iso(1) member(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) modules(0) pkcs-1(1)} DEFINITIONS EXPLICIT TAGS ::= BEGIN RSAPrivateKey ::= SEQUENCE { version Version, modulus INTEGER, publicExponent INTEGER, privateExponent INTEGER, prime1 INTEGER, prime2 INTEGER, exponent1 INTEGER, exponent2 INTEGER, coefficient INTEGER } Version ::= INTEGER END Compile ASN.1 schema into Python -------------------------------- In the best case, you should be able to automatically compile ASN.1 spec into Python classes. For that purpose we have the `asn1ate <https://github.com/kimgr/asn1ate>`_ tool: .. code-block:: bash $ asn1ate pkcs-1.asn > rsakey.py Though it may not work out as, as it stands now, asn1ate does not support all ASN.1 language constructs. Alternatively, you could check out the `pyasn1-modules <https://github.com/pyasn1/pyasn1-modules>`_ package to see if it already has the ASN.1 spec you are looking for compiled and shipped there. Then just install the package, import the data structure you need and use it: .. code-block:: bash $ pip install pyasn1-modules As a last resort, you could express ASN.1 in Python by hand. The end result should be a declarative Python code resembling original ASN.1 syntax like this: .. code-block:: python # rsakey.py class Version(Integer): pass class RSAPrivateKey(Sequence): componentType = NamedTypes( NamedType('version', Version()), NamedType('modulus', Integer()), NamedType('publicExponent', Integer()), NamedType('privateExponent', Integer()), NamedType('prime1', Integer()), NamedType('prime2', Integer()), NamedType('exponent1', Integer()), NamedType('exponent2', Integer()), NamedType('coefficient', Integer()) ) Read your ~/.ssh/id_rsa ----------------------- Given we've put our Python classes into the `rsakey.py` module, we could import the top-level object for SSH keys container and initialize it from our `~/.ssh/id_rsa` file (for sake of simplicity here we assume no passphrase is set on the key file): .. code-block:: python from base64 import b64decode from pyasn1.codec.der.decoder import decode as der_decoder from rsakey import RSAPrivateKey # Read SSH key from file (assuming no passphrase) with open('.ssh/id_rsa') as key_file: b64_serialisation = ''.join(key_file.readlines()[1:-1]) # Undo BASE64 serialisation der_serialisation = b64decode(b64_serialisation) # Undo DER serialisation, reconstruct SSH key structure private_key, rest_of_input = der_decoder(der_serialisation, asn1Spec=RSAPrivateKey()) Once we have Python ASN.1 structures initialized, we could inspect them: .. code-block:: pycon >>> print('%s' % private_key) RSAPrivateKey: version=0 modulus=280789907761334970323210643584308373... publicExponent=65537 privateExponent=1704567874679144879123080924... prime1=1780178536719561265324798296279384073... prime2=1577313184995269616049017780493740138... exponent1=1193974819720845247396384239609024... exponent2=9240965721817961178848297404494811... coefficient=10207364473358910343346707141115... Play with the keys ------------------ As well as use them nearly as we do with native Python types: .. code-block:: pycon >>> pk = private_key >>> >>> pk['prime1'] * pk['prime2'] == pk['modulus'] True >>> pk['prime1'] == pk['modulus'] // pk['prime2'] True >>> pk['exponent1'] == pk['privateExponent'] % (pk['prime1'] - 1) True >>> pk['exponent2'] == pk['privateExponent'] % (pk['prime2'] - 1) True Technically, pyasn1 classes `emulate <https://docs.python.org/3/reference/datamodel.html#emulating-container-types>`_ Python built-in types. Transform to built-ins ---------------------- ASN.1 data structures exhibit a way more complicated behaviour compared to Python types. You may wish to simplify things by turning the whole tree of pyasn1 objects into an analogous tree made of base Python types: .. code-block:: pycon >>> from pyasn1.codec.native.encoder import encode >>> ... >>> py_private_key = encode(private_key) >>> py_private_key {'version': 0, 'modulus': 280789907761334970323210643584308373, 'publicExponent': 65537, 'privateExponent': 1704567874679144879123080924, 'prime1': 1780178536719561265324798296279384073, 'prime2': 1577313184995269616049017780493740138, 'exponent1': 1193974819720845247396384239609024, 'exponent2': 9240965721817961178848297404494811, 'coefficient': 10207364473358910343346707141115} You can do vice-versa: initialize ASN.1 structure from a dict: .. code-block:: pycon >>> from pyasn1.codec.native.decoder import decode >>> py_private_key = {'modulus': 280789907761334970323210643584308373} >>> private_key = decode(py_private_key, asn1Spec=RSAPrivateKey()) Write it back ------------- Possibly not that applicable to the SSH key example, but you can of course modify any part of the ASN.1 data structure and serialise it back into the same or other wire representation: .. code-block:: python from pyasn1.codec.der.encoder import encode as der_encoder # Serialise SSH key data structure into DER stream der_serialisation = der_encoder(private_key) # Serialise DER stream into BASE64 stream b64_serialisation = '-----BEGIN RSA PRIVATE KEY-----\n' b64_serialisation += b64encode(der_serialisation) b64_serialisation += '-----END RSA PRIVATE KEY-----\n' with open('.ssh/id_rsa.new', 'w') as key_file: key_file.write(b64_serialisation)	6.25 KB	2024-11-26 17:32
📄 index.rst Index ===== .. Make RTD happy. We have a redirect index.html to contents.html. :ref:`Start Content`	103 B	2024-11-26 17:32
📄 license.rst .. _license: License ======= .. include:: ../../LICENSE.rst	62 B	2024-11-26 17:32
📁 pyasn1	-	2024-11-26 17:32

Terminal