I’m seeing these errors a fair bit in an image that works well otherwise for a while, full stack attached. Ideas? ObjectMemory versionId #[72 47 75 112 70 33 0 0 72 47 75 112] OS Name: Microsoft Windows 8.1 Pro OS Version: 6.3.9600 N/A Build 9600 bad argument 1 Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: Xtreams.BCrypt(ExternalInterface)>>externalAccessFailed Xtreams.BCrypt>>BCryptGenRandom:with:with:with: ExternalMethod>>unlinkedCall:arguments: Xtreams.BCrypt>>genRandom:buffer:count: Xtreams.BCryptRandom>>read:into: Xtreams.RandomReadStream>>read:into:at: optimized [] in Xtreams.WriteStream>>streamingWrite:from: BlockClosure>>on:do: Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>streamingWrite:from: Xtreams.RandomReadStream(Xtreams.ReadStream)>>streamingWrite:into: Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>write:from: Xtreams.TLSContext>>newRandom Xtreams.TLSContext>>newClientHello Xtreams.TLSConnection>>newClientHello Xtreams.TLSHandshake>>sendClientHello optimized [] in Xtreams.TLSHandshake>>connect UndefinedObject>>ifNil: Xtreams.TLSHandshake>>connect BlockClosure>>tlsConnect: optimized [] in Xtreams.TLSConnection>>connect: Xtreams.TLSConnection>>writeProtectDo: Xtreams.TLSConnection>>connect: optimized [] in Net.TLSConnection>>startTLS BlockClosure>>ifCurtailed: Net.HttpsConnection(Net.TLSConnection)>>startTLS Net.HttpsConnection(Net.TLSConnection)>>openStreamFor:port:timeout: Net.HttpProtocolInterpreter(Net.NetProtocolInterpreter)>>connectToHost:port:timeout: Net.HttpProtocolInterpreter>>connect Net.HttpProtocolInterpreter>>executeRequest: Net.HttpClient>>privateExecuteRequest Net.HttpClient>>executeRequestDo: -Boris DeepCove Labs _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc 7.10.1 bad argument 1.txt (51K) Download Attachment |
HttpsConnection defaultTLSContext random source self: a Xtreams.BCryptRandom hash: 3449 identity: 3449 library: a Xtreams.BCrypt provider: a CPointer {invalid} (void * ) … and this “fixes” it, but I can’t help feeling like this isn’t supposed to be exposed like so? [HttpsConnection defaultTLSContext: nil] on: Error do: [:ex | ex proceed] -Boris DeepCove Labs From: [hidden email] [mailto:[hidden email]]
On Behalf Of Boris Slobodin, DeepCove Labs I’m seeing these errors a fair bit in an image that works well otherwise for a while, full stack attached. Ideas? ObjectMemory versionId #[72 47 75 112 70 33 0 0 72 47 75 112] OS Name: Microsoft Windows 8.1 Pro OS Version: 6.3.9600 N/A Build 9600 bad argument 1 Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: Xtreams.BCrypt(ExternalInterface)>>externalAccessFailed Xtreams.BCrypt>>BCryptGenRandom:with:with:with: ExternalMethod>>unlinkedCall:arguments: Xtreams.BCrypt>>genRandom:buffer:count: Xtreams.BCryptRandom>>read:into: Xtreams.RandomReadStream>>read:into:at: optimized [] in Xtreams.WriteStream>>streamingWrite:from: BlockClosure>>on:do: Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>streamingWrite:from: Xtreams.RandomReadStream(Xtreams.ReadStream)>>streamingWrite:into: Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>write:from: Xtreams.TLSContext>>newRandom Xtreams.TLSContext>>newClientHello Xtreams.TLSConnection>>newClientHello Xtreams.TLSHandshake>>sendClientHello optimized [] in Xtreams.TLSHandshake>>connect UndefinedObject>>ifNil: Xtreams.TLSHandshake>>connect BlockClosure>>tlsConnect: optimized [] in Xtreams.TLSConnection>>connect: Xtreams.TLSConnection>>writeProtectDo: Xtreams.TLSConnection>>connect: optimized [] in Net.TLSConnection>>startTLS BlockClosure>>ifCurtailed: Net.HttpsConnection(Net.TLSConnection)>>startTLS Net.HttpsConnection(Net.TLSConnection)>>openStreamFor:port:timeout: Net.HttpProtocolInterpreter(Net.NetProtocolInterpreter)>>connectToHost:port:timeout: Net.HttpProtocolInterpreter>>connect Net.HttpProtocolInterpreter>>executeRequest: Net.HttpClient>>privateExecuteRequest Net.HttpClient>>executeRequestDo: -Boris DeepCove Labs _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Boris Popov, DeepCove Labs (SNN)
This looks like the default context is being saved with the image and not flushed on startup. Since the random instance is tied to an external resource it cannot be reused after restart from a snapshot.
HTH, Martin "Boris Slobodin, DeepCove Labs"<[hidden email]> wrote: > Date: November 5, 2014 10:50:25 AM > From: "Boris Slobodin, DeepCove Labs" <[hidden email]> > To: "[hidden email]"<[hidden email]> > Subject: Re: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > > This looks to be an issue, > > HttpsConnection defaultTLSContext random source > > self: a Xtreams.BCryptRandom > hash: 3449 > identity: 3449 > library: a Xtreams.BCrypt > provider: a CPointer {invalid} (void * ) > > ... and this "fixes" it, but I can't help feeling like this isn't supposed to be exposed like so? > > [HttpsConnection defaultTLSContext: nil] on: Error do: [:ex | ex proceed] > > -Boris > DeepCove Labs > > From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Slobodin, DeepCove Labs > Sent: Wednesday, November 5, 2014 7:32 AM > To: [hidden email] > Subject: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > > I'm seeing these errors a fair bit in an image that works well otherwise for a while, full stack attached. Ideas? > > ObjectMemory versionId #[72 47 75 112 70 33 0 0 72 47 75 112] > > OS Name: Microsoft Windows 8.1 Pro > OS Version: 6.3.9600 N/A Build 9600 > > bad argument 1 > Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > Xtreams.BCrypt(ExternalInterface)>>externalAccessFailed > Xtreams.BCrypt>>BCryptGenRandom:with:with:with: > ExternalMethod>>unlinkedCall:arguments: > Xtreams.BCrypt>>genRandom:buffer:count: > Xtreams.BCryptRandom>>read:into: > Xtreams.RandomReadStream>>read:into:at: > optimized [] in Xtreams.WriteStream>>streamingWrite:from: > BlockClosure>>on:do: > Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>streamingWrite:from: > Xtreams.RandomReadStream(Xtreams.ReadStream)>>streamingWrite:into: > Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>write:from: > Xtreams.TLSContext>>newRandom > Xtreams.TLSContext>>newClientHello > Xtreams.TLSConnection>>newClientHello > Xtreams.TLSHandshake>>sendClientHello > optimized [] in Xtreams.TLSHandshake>>connect > UndefinedObject>>ifNil: > Xtreams.TLSHandshake>>connect > BlockClosure>>tlsConnect: > optimized [] in Xtreams.TLSConnection>>connect: > Xtreams.TLSConnection>>writeProtectDo: > Xtreams.TLSConnection>>connect: > optimized [] in Net.TLSConnection>>startTLS > BlockClosure>>ifCurtailed: > Net.HttpsConnection(Net.TLSConnection)>>startTLS > Net.HttpsConnection(Net.TLSConnection)>>openStreamFor:port:timeout: > Net.HttpProtocolInterpreter(Net.NetProtocolInterpreter)>>connectToHost:port:timeout: > Net.HttpProtocolInterpreter>>connect > Net.HttpProtocolInterpreter>>executeRequest: > Net.HttpClient>>privateExecuteRequest > Net.HttpClient>>executeRequestDo: > > -Boris > DeepCove Labs > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Right, I realize as much, then is the flush on startup missing by design or an oversight that should be corrected? I can stuff it into our subsystem but may be better if it was taken care of elsewhere in future releases.
-Boris > On Nov 5, 2014, at 19:36, "[hidden email]" <[hidden email]> wrote: > > This looks like the default context is being saved with the image and not flushed on startup. Since the random instance is tied to an external resource it cannot be reused after restart from a snapshot. > > HTH, > > Martin > > "Boris Slobodin, DeepCove Labs"<[hidden email]> wrote: >> Date: November 5, 2014 10:50:25 AM >> From: "Boris Slobodin, DeepCove Labs" <[hidden email]> >> To: "[hidden email]"<[hidden email]> >> Subject: Re: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: >> >> This looks to be an issue, >> >> HttpsConnection defaultTLSContext random source >> >> self: a Xtreams.BCryptRandom >> hash: 3449 >> identity: 3449 >> library: a Xtreams.BCrypt >> provider: a CPointer {invalid} (void * ) >> >> ... and this "fixes" it, but I can't help feeling like this isn't supposed to be exposed like so? >> >> [HttpsConnection defaultTLSContext: nil] on: Error do: [:ex | ex proceed] >> >> -Boris >> DeepCove Labs >> >> From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Slobodin, DeepCove Labs >> Sent: Wednesday, November 5, 2014 7:32 AM >> To: [hidden email] >> Subject: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: >> >> I'm seeing these errors a fair bit in an image that works well otherwise for a while, full stack attached. Ideas? >> >> ObjectMemory versionId #[72 47 75 112 70 33 0 0 72 47 75 112] >> >> OS Name: Microsoft Windows 8.1 Pro >> OS Version: 6.3.9600 N/A Build 9600 >> >> bad argument 1 >> Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: >> Xtreams.BCrypt(ExternalInterface)>>externalAccessFailed >> Xtreams.BCrypt>>BCryptGenRandom:with:with:with: >> ExternalMethod>>unlinkedCall:arguments: >> Xtreams.BCrypt>>genRandom:buffer:count: >> Xtreams.BCryptRandom>>read:into: >> Xtreams.RandomReadStream>>read:into:at: >> optimized [] in Xtreams.WriteStream>>streamingWrite:from: >> BlockClosure>>on:do: >> Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>streamingWrite:from: >> Xtreams.RandomReadStream(Xtreams.ReadStream)>>streamingWrite:into: >> Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>write:from: >> Xtreams.TLSContext>>newRandom >> Xtreams.TLSContext>>newClientHello >> Xtreams.TLSConnection>>newClientHello >> Xtreams.TLSHandshake>>sendClientHello >> optimized [] in Xtreams.TLSHandshake>>connect >> UndefinedObject>>ifNil: >> Xtreams.TLSHandshake>>connect >> BlockClosure>>tlsConnect: >> optimized [] in Xtreams.TLSConnection>>connect: >> Xtreams.TLSConnection>>writeProtectDo: >> Xtreams.TLSConnection>>connect: >> optimized [] in Net.TLSConnection>>startTLS >> BlockClosure>>ifCurtailed: >> Net.HttpsConnection(Net.TLSConnection)>>startTLS >> Net.HttpsConnection(Net.TLSConnection)>>openStreamFor:port:timeout: >> Net.HttpProtocolInterpreter(Net.NetProtocolInterpreter)>>connectToHost:port:timeout: >> Net.HttpProtocolInterpreter>>connect >> Net.HttpProtocolInterpreter>>executeRequest: >> Net.HttpClient>>privateExecuteRequest >> Net.HttpClient>>executeRequestDo: >> >> -Boris >> DeepCove Labs >> >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Without looking into it, my knee jerk reaction would be that it should be the HTTPS package's responsibility, since that seems to be where the TLS context is cached.
"Boris Slobodin, DeepCove Labs"<[hidden email]> wrote: > Right, I realize as much, then is the flush on startup missing by design or an oversight that should be corrected? I can stuff it into our subsystem but may be better if it was taken care of elsewhere in future releases. > > -Boris > > > On Nov 5, 2014, at 19:36, "[hidden email]" <[hidden email]> wrote: > > > > This looks like the default context is being saved with the image and not flushed on startup. Since the random instance is tied to an external resource it cannot be reused after restart from a snapshot. > > > > HTH, > > > > Martin > > > > "Boris Slobodin, DeepCove Labs"<[hidden email]> wrote: > >> Date: November 5, 2014 10:50:25 AM > >> From: "Boris Slobodin, DeepCove Labs" <[hidden email]> > >> To: "[hidden email]"<[hidden email]> > >> Subject: Re: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > >> > >> This looks to be an issue, > >> > >> HttpsConnection defaultTLSContext random source > >> > >> self: a Xtreams.BCryptRandom > >> hash: 3449 > >> identity: 3449 > >> library: a Xtreams.BCrypt > >> provider: a CPointer {invalid} (void * ) > >> > >> ... and this "fixes" it, but I can't help feeling like this isn't supposed to be exposed like so? > >> > >> [HttpsConnection defaultTLSContext: nil] on: Error do: [:ex | ex proceed] > >> > >> -Boris > >> DeepCove Labs > >> > >> From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Slobodin, DeepCove Labs > >> Sent: Wednesday, November 5, 2014 7:32 AM > >> To: [hidden email] > >> Subject: [vwnc] [7.10.1] Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > >> > >> I'm seeing these errors a fair bit in an image that works well otherwise for a while, full stack attached. Ideas? > >> > >> ObjectMemory versionId #[72 47 75 112 70 33 0 0 72 47 75 112] > >> > >> OS Name: Microsoft Windows 8.1 Pro > >> OS Version: 6.3.9600 N/A Build 9600 > >> > >> bad argument 1 > >> Xtreams.BCrypt(ExternalInterface)>>externalAccessFailedWith: > >> Xtreams.BCrypt(ExternalInterface)>>externalAccessFailed > >> Xtreams.BCrypt>>BCryptGenRandom:with:with:with: > >> ExternalMethod>>unlinkedCall:arguments: > >> Xtreams.BCrypt>>genRandom:buffer:count: > >> Xtreams.BCryptRandom>>read:into: > >> Xtreams.RandomReadStream>>read:into:at: > >> optimized [] in Xtreams.WriteStream>>streamingWrite:from: > >> BlockClosure>>on:do: > >> Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>streamingWrite:from: > >> Xtreams.RandomReadStream(Xtreams.ReadStream)>>streamingWrite:into: > >> Xtreams.TLSMarshalingWriteStream(Xtreams.WriteStream)>>write:from: > >> Xtreams.TLSContext>>newRandom > >> Xtreams.TLSContext>>newClientHello > >> Xtreams.TLSConnection>>newClientHello > >> Xtreams.TLSHandshake>>sendClientHello > >> optimized [] in Xtreams.TLSHandshake>>connect > >> UndefinedObject>>ifNil: > >> Xtreams.TLSHandshake>>connect > >> BlockClosure>>tlsConnect: > >> optimized [] in Xtreams.TLSConnection>>connect: > >> Xtreams.TLSConnection>>writeProtectDo: > >> Xtreams.TLSConnection>>connect: > >> optimized [] in Net.TLSConnection>>startTLS > >> BlockClosure>>ifCurtailed: > >> Net.HttpsConnection(Net.TLSConnection)>>startTLS > >> Net.HttpsConnection(Net.TLSConnection)>>openStreamFor:port:timeout: > >> Net.HttpProtocolInterpreter(Net.NetProtocolInterpreter)>>connectToHost:port:timeout: > >> Net.HttpProtocolInterpreter>>connect > >> Net.HttpProtocolInterpreter>>executeRequest: > >> Net.HttpClient>>privateExecuteRequest > >> Net.HttpClient>>executeRequestDo: > >> > >> -Boris > >> DeepCove Labs > >> > >> > >> > >> > >> _______________________________________________ > >> vwnc mailing list > >> [hidden email] > >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |