From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 27E751F725; Tue, 15 Mar 2016 23:30:24 +0000 (UTC) Date: Tue, 15 Mar 2016 23:30:24 +0000 From: Eric Wong To: "Shota Fukumori (sora_h)" Cc: russm , unicorn-public@bogomips.org, yahns-public@yhbt.net Subject: Re: https://unicorn.bogomips.org accepts client certificate? Message-ID: <20160315233024.GA11461@dcvr.yhbt.net> References: <20160315085851.GA505@dcvr.yhbt.net> <20160315094348.GB7123@ha.slofith.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: "Shota Fukumori (sora_h)" wrote: > To be clear, you have to have a client certificate on your certificate > manager to be prompted. > Server doesn't specify acceptable client certificate CA names, so any > client certificate is ok. Thanks for the report, I think I just fixed the problem: ctx.set_params # reasonable defaults for clients, apparently However, webrick and drb both set VERIFY_NONE for servers: ctx.set_params(verify_mode: OpenSSL::SSL::VERIFY_NONE) I've updated https://unicorn.bogomips.org/ with the above change, can you confirm it works for you? If so, I'll update the yahns documentation.