From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) by sourceware.org (Postfix) with ESMTPS id D7AF9386F448 for ; Mon, 28 Sep 2020 21:41:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D7AF9386F448 Received: by mail-oi1-x234.google.com with SMTP id x14so3043791oic.9 for ; Mon, 28 Sep 2020 14:41:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LzttyXsCp41xDj+kmeT/jiCvl+V3AcDuONfN27nCYhM=; b=cs7FKHRg9taf0hh51QP9Z2B5dZH1Y26AZZM9L8E1D+xmojAM5eX8mAQ4+vubmWykFA xBS0WvaliIpx9P3dmy+xnP5ue5sSovX7bZF1+R62wm95IVaf00cxc7e4oDby0qyur4Dl nQKEKMSgSh1ZsbPJbMGkmhP6cqBqxDu6jrv77tCyCVSCEH9kjlLf4TJgTl42mtsfr/pB H4Hm287wvT52WeJSfcgdZSmfYh2ua6gbkCcuvKmNudSCg6UsRdQGgQ4TIF6RV7AeERyI C2wLfQJmx8mWmEUrYU8MIREJcEYsa2GZ6AD8AAY3c/ckhRjJYqF3Baa1MMLYq2QC9Mck oImw== X-Gm-Message-State: AOAM53013k9OQGWZLaD0Uwc+qDR/ElSlTlyr2j+qD7eigRcVq3Q9eyey SUwnkeMsSpB9oQfVu16JtApmwXVU7x+FBrOS7jDgMVw6lG+vLQ== X-Google-Smtp-Source: ABdhPJxuKbaq8phDXevKkE7UJDbeXrwJ0iEJUhwtZGqgd/UiwPvRhiNghEgp9Jeh9IMBZy7GqdqypOmgNLq73arAtk8= X-Received: by 2002:aca:a905:: with SMTP id s5mr544375oie.93.1601329269302; Mon, 28 Sep 2020 14:41:09 -0700 (PDT) MIME-Version: 1.0 References: <3f057cc9-831c-04a7-d390-32015178176e@lassi.io> In-Reply-To: <3f057cc9-831c-04a7-d390-32015178176e@lassi.io> From: Arvydas Silanskas Date: Tue, 29 Sep 2020 00:40:57 +0300 Message-ID: Subject: Re: Kawa and SSL/TLS To: Lassi Kortela Cc: kawa mailing list X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: kawa@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Kawa mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2020 21:41:11 -0000 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 ra=C5=A1=C4=97: > > 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. >