From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: ANN: Ada/SPARK ASN.1 implementation version 0.0.01
Date: Mon, 1 Aug 2016 10:51:47 +0200
Organization: Aioe.org NNTP Server
Message-ID: <nnn2j8$1dgr$1@gioia.aioe.org>
References: <3ac0fbcd-1f1c-40b8-b030-de03954f894f@googlegroups.com>
NNTP-Posting-Host: xelDFTENDI+dlkJFd2Ot2w.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:31238
Date: 2016-08-01T10:51:47+02:00
List-Id: <comp.lang.ada>

On 2016-08-01 10:15, Shark8 wrote:
> I'm making public my ASN.1 project which aims to be a verified
> implementation of ASN.1, which is used in security-certificates, which
> is hopefully the first step in a verified-TLS/-TLS -- the project also
> aims to be [directly] usable in DSA projects.
>
> As of 0.0.01 the only portion implemented is a pure big-number
> package, and another currently shared-passive unit for usability.
>
> I would certainly appropriate comments, criticism, and most
> especially  contributions.

I am interested in the TLS interface outline. Specifically, in how easy 
it would be to integrate into a non-blocking socket-I/O driven architecture.

That means the TLS layer should write no more data than the output 
buffer length, while keeping its internal state to continue when the 
buffer becomes available, and the layer is called again.

Same when reading data from the input buffer, data get available in 
chunks of arbitrary size. If the layer expects more data, it must return 
to the caller, again, keeping internal state.

This certainly would have impact on the implementation.

P.S. Simple Components presently use GNUTLS for HTTPS, SMTP, MQTT. It 
would be great to have a native Ada TLS instead.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de