From owner-freebsd-questions@FreeBSD.ORG Sat Feb 7 16:30:21 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDE348E3 for ; Sat, 7 Feb 2015 16:30:21 +0000 (UTC) Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD8D8A5E for ; Sat, 7 Feb 2015 16:30:21 +0000 (UTC) Received: by iecrd18 with SMTP id rd18so7995488iec.9 for ; Sat, 07 Feb 2015 08:30:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=EAQi+Nu7kvZWLvBUE8Z2COQR9LLt98as93blzq42NBE=; b=vWaCHVDzAf3bLZ5SmlWUwLTm9xY4DF7hfxLM9rIxAat6tMack2iTF+lDZE+DqhxW4i KjD9b3OoFOXSLUBoznB62QcHnSbojwT9EZL5YvbAfPzoxiFWyqpiVRkitYWZ5yhymWod /R/QUDQVY9jHY5egNGNHhrIdO87kbZtudwgZgHDERKKYPiPGIs53KOubzIEKaPSgA3Op IzfhhmoQlADlkMqtOjLdsXSSvEZbnuxotQqrJXmm+ri4Qc6XpZeyU8T03DbM/8LJsf1M pftQT6Cwb74OwL7YsA9QyY4N0VEghJiBAccB3BHwAZYvn78f5Aw2aIgqPWk95w7v3LYT ekkw== MIME-Version: 1.0 X-Received: by 10.50.79.135 with SMTP id j7mr8114372igx.32.1423326611358; Sat, 07 Feb 2015 08:30:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.7 with HTTP; Sat, 7 Feb 2015 08:30:11 -0800 (PST) In-Reply-To: References: Date: Sat, 7 Feb 2015 08:30:11 -0800 X-Google-Sender-Auth: NL9SEZA1iaXRzFWs8sQfECIDXB8 Message-ID: Subject: Re: HTTPS/TLS issue on a NDIS wrapped NIC From: Adrian Chadd To: Simone Lombardo Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2015 16:30:22 -0000 .. or if that isn't breaking things, maybe there's some packet corruption going on that triggers encryption failures? Normally a corrupted packet would just be dropped by some part of the stack. -adrian