From: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
To: Lassi Kortela <lassi@lassi.io>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Kawa and SSL/TLS
Date: Tue, 29 Sep 2020 00:40:57 +0300 [thread overview]
Message-ID: <CAPh7weD63B1ykqvC-N_O7osT6KO0YsdFwhJkNGewoa6ue3P+qg@mail.gmail.com> (raw)
In-Reply-To: <3f057cc9-831c-04a7-d390-32015178176e@lassi.io>
I made an example of an ssl server socket, which prints to the console what
it receives https://github.com/arvyy/kawa-ssl-socket-example (instructions
included in repo)
2020-09-28, pr, 15:08 Lassi Kortela <lassi@lassi.io> rašė:
> > 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.
>
next prev parent reply other threads:[~2020-09-28 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 10:45 Lassi Kortela
2020-09-28 11:52 ` Arvydas Silanskas
2020-09-28 12:08 ` Lassi Kortela
2020-09-28 21:40 ` Arvydas Silanskas [this message]
2020-09-29 14:09 ` Lassi Kortela
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=CAPh7weD63B1ykqvC-N_O7osT6KO0YsdFwhJkNGewoa6ue3P+qg@mail.gmail.com \
--to=nma.arvydas.silanskas@gmail.com \
--cc=kawa@sourceware.org \
--cc=lassi@lassi.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).