On Mon, Apr 17, 2017 at 10:29:31AM +0000, Paul Chakravarti wrote: > >On 2017-04-17, David Coppa <dco...@gmail.com> wrote: > >> On Sun, Apr 16, 2017 at 11:17 AM, Paul Chakravarti <pc...@outlook.com> > >> wrote: > >>> Hello, > >>> > >>> I am trying out vmm on 6.1 and can setup/boot vm etc. however when I try > >>> to > >>> download a large file using SSL I consistenetly get the following error: > >>> > >>>> SSL read error: read failed: error:06FFF064:digital envelope > >>> routines:CRYPTO_internal:bad decrypt > >>> > >>> This occasionally (but not always) correlates with the following message > >>> in > >>> the vmd log: > >>> > >>>> vionet queue notify - no space, dropping packet > >>> > >>> Strangely non-SSL and smaller SSL downloads seem to work ok (see below). > >>> > >>> Originally spotted this using installer but can recreate from shell. > >>> > >>> Any ideas? > >> > >> See http://marc.info/?l=openbsd-misc&m=148858752003261 > >> > >> It's a known problem. > > > >I've seen corruption with non-SSL network transfers too. It's just more > >obvious with SSL because in that case the session gets killed, whereas > >otherwise the corrupt input is silently accepsilently accepted. > > > > It does seem more prevalent with SSL transfers - the SHA256s of the files > transferred vis http are correct (over several transfers) while there is > always an always an error on the https transfers from the same site. > > Interestingly the problem only seems to come up on 'fast' connections - > possibly something CPU related (cpu load exacerbated by SSL?). I'm still not > sure why the TCP layer doesn't sort out the dropped packets though. > > # ftp -Vo- https://ftp.openbsd.org/pub/OpenBSD/6.1/amd64/bsd | sha256 > > 440311305f27f0efcfcc88116299a21cb3f890fb91ee611c2a79cc9163e8fceb > # > # > # ftp -Vo- https://mirrorservice.org/pub/OpenBSD/6.1/amd64/bsd | sha256 > ftp: SSL read error: read failed: error:06FFF064:digital envelope > routines:CRYPTO_internal:bad decrypt
I think I know what's going on, I just haven't had time to sort through it yet. I don't think it's related to the network stack, FWIW. -ml
