From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lassi@lassi.io>
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net
 [217.70.183.197])
 by sourceware.org (Postfix) with ESMTPS id 454F538618E2
 for <kawa@sourceware.org>; Mon, 28 Sep 2020 12:08:18 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 454F538618E2
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=lassi.io
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=lassi@lassi.io
X-Originating-IP: 82.181.134.218
Received: from sunshower.local (82-181-134-218.bb.dnainternet.fi
 [82.181.134.218]) (Authenticated sender: lassi@lassi.io)
 by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id A506B1C000A;
 Mon, 28 Sep 2020 12:08:16 +0000 (UTC)
Subject: Re: Kawa and SSL/TLS
To: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
References: <a9b41e1c-f2c5-d9ac-d4b3-402b2b06f6c4@lassi.io>
 <CAPh7weDreOun6y0HHpJQNqZZk=Xi-xy3Xv2V_nC=qgD2Nvv62A@mail.gmail.com>
From: Lassi Kortela <lassi@lassi.io>
Message-ID: <3f057cc9-831c-04a7-d390-32015178176e@lassi.io>
Date: Mon, 28 Sep 2020 15:08:15 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
 Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CAPh7weDreOun6y0HHpJQNqZZk=Xi-xy3Xv2V_nC=qgD2Nvv62A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: kawa@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Kawa mailing list <kawa.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/kawa>,
 <mailto:kawa-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/kawa/>
List-Post: <mailto:kawa@sourceware.org>
List-Help: <mailto:kawa-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/kawa>,
 <mailto:kawa-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2020 12:08:19 -0000

> Plugging in the sense of writing a wrapper with more idiomatic scheme 
> api, or just using?

Eventually a nice wrapper, but getting it working at all would be a good 
start :)

> If it's the later and you want to see how to get 
> some specific usecase working, I could play around with it in the 
> evening and see what I get.

Great, thanks! That would be awesome.

TLS support in Scheme implementations is uneven and doesn't have a 
standard interface. To that end, I'd like to write a "TLS pipe" SRFI 
that provides the same API on all supported Schemes, irrespective of 
which backend library is used as the TLS implementation. The SRFI should 
be written so that it works on JVM schemes as well, instead of assuming 
that all the world is C and OpenSSL. A working Kawa implementation would 
be a good way to ensure portability.