PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Peter,
>
> On 12/22/16 12:52 PM, Peter Wallis wrote:
> > Ahh! changed the server.xml entries to 8443 tried: openssl s_client
> > -connect 192.168.1.149:8443 and got: CONNECTED(0003)
> > 3074541192:error:140790E5SSL routhines
:27, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Peter,
>
> On 12/22/16 11:03 AM, Peter Wallis wrote:
> > Hi Christopher, re 443 on *nix; yes, set AUTHBIND='yes' in
> > /etc/defaults/
out but it seems we are looking for
something I've done that is weird.
P
On 22 December 2016 at 15:38, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Peter,
>
> On 12/22/16 2:43 AM, Peter Wallis wrote:
&
016 at 21:17, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Peter,
>
> On 12/21/16 4:22 AM, Peter Wallis wrote:
> > Hi all, I have tomcat 8.0.39 running on a raspberry pi (easy) and
> > though
using -Djavax.net.debug=all ...
what am I expecting to happen?
The only action I get is the line (which happens normally)
- - "HEAD / HTTP/1.1" 200 -
in my connector's access log.
On 21 December 2016 at 14:53, Peter Wallis wrote:
> Hi Hassan,
> yes, but ... that says
javax.net.debug=ssl:handshake:data
on the startup script (thanks Martin)
- trying now...
P
On 21 December 2016 at 14:31, Hassan Schroeder
wrote:
> On Wed, Dec 21, 2016 at 1:22 AM, Peter Wallis wrote:
>
> > Can someone point me to the official how-to debug ssl issues on tomcat?
>
>
Hi all,
I have tomcat 8.0.39 running on a raspberry pi (easy) and thought I'd try
setting it up to provide "skills" for the Amazon Echo Alexa service. This
requires a url which "presents" either a signed certificate, or a
self-signed certificate.
Using fiirefox to check, I believe I got it pres
