search for: wtls

...uing csr, signing certs with that particular curve. Printing certs and verifying certs against keys is panning out too, comparing md5 hashes also no errors. So why would openssl not accept (limit) keys is has generated and verified with no error? [ openssl ecparam -list_curves ] ? secp112r1 : SECG/WTLS curve over a 112 bit prime field ? secp112r2 : SECG curve over a 112 bit prime field ? secp128r1 : SECG curve over a 128 bit prime field ? secp128r2 : SECG curve over a 128 bit prime field ? secp160k1 : SECG curve over a 160 bit prime field ? secp160r1 : SECG curve over a 160 bit prime field ? secp...

> On 30 July 2018 at 20:37 ????? <vtol at gmx.net> wrote: > > > > >>>>>>> facing [ no shared cipher ] error with EC private keys. > >>>>>> the client connecting to your instance has to support ecdsa > >>>>>> > >>>>>> > >>>>> It does - Thunderbird 60.0b10 (64-bit) >

...t;div> would openssl not accept (limit) keys is has generated and verified with </div> <div> no error? </div> <div> <br> </div> <div> [ openssl ecparam -list_curves ] </div> <div> secp112r1 : SECG/WTLS curve over a 112 bit prime field </div> <div> secp112r2 : SECG curve over a 112 bit prime field </div> <div> secp128r1 : SECG curve over a 128 bit prime field </div> <div> secp128r2 : SECG curve over a 128 bit prime field &l...

this bug is similar to something i see already discussed on why''s blogpost comments, which was reported fixed, but that was before the gem was made available (which is what im using since i cant seem to access the C.WTLS SVN) my guess is one of 3 things: fix didnt propagate to gem, my own failure to make an educated guess on proper setup (1), or a genuine bug essentially, for @slice in @toasts render :partial "slice" messing around with :object => slice (or @slice) the best i can get is @slice...

I was wondering how to give the Ruby on Rails console a web interface like this website http://tryruby.hobix.com/. -- Posted via http://www.ruby-forum.com/.