All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: <rust-for-linux@vger.kernel.org>
Subject: ASN.1
Date: Tue, 21 May 2024 09:36:00 +0300	[thread overview]
Message-ID: <D1F44P3VLTBN.30LUQ60X5J3DN@kernel.org> (raw)

Hi,

There's one application where it would make a lot of sense to have the
core implementation in Rust, and make it callable from C. It is encoding
and decoding of ASN.1 (DER).

It is essentially hierarchical binary parsing, i.e. exactly kind of
stuff where it is too easy to shoot yourself into foot with C.

So question is how to approach this? How the holding data structure for
holding the deserialized data should represented so that is is also
directly accessible from C?

Maybe not the sexiest application ever, but it is an actual applications
where Rust might weight a lot, also for the C code base ;-)

I'm interested to help with this too as I consume a lot of DER type of
input data... so I know what it should look like to work at all for the
C code. Or do not know at this poinnt, but can verify the sensibility
at minimum :-)

BR, Jarkko

             reply	other threads:[~2024-05-21  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  6:36 Jarkko Sakkinen [this message]
2024-05-21 14:52 ` ASN.1 Miguel Ojeda
2024-05-21 15:20   ` ASN.1 Jarkko Sakkinen
2024-05-21 18:01     ` ASN.1 Jarkko Sakkinen
2024-05-21 18:55       ` ASN.1 Jarkko Sakkinen
2024-05-22 12:04         ` ASN.1 Alex Gaynor
2024-05-22 12:56           ` ASN.1 Jarkko Sakkinen
2024-05-22 13:49             ` ASN.1 Jarkko Sakkinen
2024-05-23  7:00               ` ASN.1 Jarkko Sakkinen
2024-05-23  7:03                 ` ASN.1 Jarkko Sakkinen
2024-05-23 15:44                 ` ASN.1 Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D1F44P3VLTBN.30LUQ60X5J3DN@kernel.org \
    --to=jarkko@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.