Debug info on NSS tools

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Debug info on NSS tools

John Jiang
Can NSS tools, like selfserv and tstclnt, output debug info?
My NSS binary is built with debug mode.

I try to enable the debug logs for selfserv and tstclnt, but don't get any
useful option.
Option -v just outputs a bit more logs. That's not enough for me.
I wish the tools can output more details on TLS handshaking.
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

Martin Thomson
Try exporting SSLTRACE=100.

That might be too much detail, but lower numbers are still useful.  I find
that 20-ish gets some fairly useful logging.

On Thu, Jan 3, 2019 at 6:12 PM John Jiang <[hidden email]> wrote:

> Can NSS tools, like selfserv and tstclnt, output debug info?
> My NSS binary is built with debug mode.
>
> I try to enable the debug logs for selfserv and tstclnt, but don't get any
> useful option.
> Option -v just outputs a bit more logs. That's not enough for me.
> I wish the tools can output more details on TLS handshaking.
> --
> dev-tech-crypto mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

John Jiang
Just tried it, but looked not work.

$ export SSLDEBUG=1
$ export SSLTRACE=127
$ tstclnt -v ...
I didn't get more logs.

On Thu, Jan 3, 2019 at 3:46 PM Martin Thomson <[hidden email]> wrote:

> Try exporting SSLTRACE=100.
>
> That might be too much detail, but lower numbers are still useful.  I find
> that 20-ish gets some fairly useful logging.
>
> On Thu, Jan 3, 2019 at 6:12 PM John Jiang <[hidden email]>
> wrote:
>
> > Can NSS tools, like selfserv and tstclnt, output debug info?
> > My NSS binary is built with debug mode.
> >
> > I try to enable the debug logs for selfserv and tstclnt, but don't get
> any
> > useful option.
> > Option -v just outputs a bit more logs. That's not enough for me.
> > I wish the tools can output more details on TLS handshaking.
> > --
> > dev-tech-crypto mailing list
> > [hidden email]
> > https://lists.mozilla.org/listinfo/dev-tech-crypto
> >
> --
> dev-tech-crypto mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

Kai Engert-4
Does this page help?
You might need a debug build (i.e. build yourself with debugging enabled).

https://wiki.mozilla.org/NSS:Tracing

Kai

On 03.01.19 13:51, John Jiang wrote:
> Just tried it, but looked not work.
>
> $ export SSLDEBUG=1
> $ export SSLTRACE=127
> $ tstclnt -v ...
> I didn't get more logs.
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

John Jiang
I had read that page. In fact, SSLDEBUG and SSLTRACE were used in my last
try.
My NSS was built with "BUILD_OPT=0", so I supposed it is a debug build.
How can I double-check this point?

Thanks!

On Sat, Jan 5, 2019 at 12:34 AM Kai Engert <[hidden email]> wrote:

> Does this page help?
> You might need a debug build (i.e. build yourself with debugging enabled).
>
> https://wiki.mozilla.org/NSS:Tracing
>
> Kai
>
> On 03.01.19 13:51, John Jiang wrote:
> > Just tried it, but looked not work.
> >
> > $ export SSLDEBUG=1
> > $ export SSLTRACE=127
> > $ tstclnt -v ...
> > I didn't get more logs.
>
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

Martin Thomson
You need to build a debug build with -DDEBUG. Disabling optimization is a
different thing.

The default build with build.sh or make nss_build_all should be fine.

On Sat, 5 Jan. 2019, 11:40 John Jiang <[hidden email] wrote:

> I had read that page. In fact, SSLDEBUG and SSLTRACE were used in my last
> try.
> My NSS was built with "BUILD_OPT=0", so I supposed it is a debug build.
> How can I double-check this point?
>
> Thanks!
>
> On Sat, Jan 5, 2019 at 12:34 AM Kai Engert <[hidden email]> wrote:
>
> > Does this page help?
> > You might need a debug build (i.e. build yourself with debugging
> enabled).
> >
> > https://wiki.mozilla.org/NSS:Tracing
> >
> > Kai
> >
> > On 03.01.19 13:51, John Jiang wrote:
> > > Just tried it, but looked not work.
> > >
> > > $ export SSLDEBUG=1
> > > $ export SSLTRACE=127
> > > $ tstclnt -v ...
> > > I didn't get more logs.
> >
> --
> dev-tech-crypto mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto
Reply | Threaded
Open this post in threaded view
|

Re: Debug info on NSS tools

John Jiang
On Sun, Jan 6, 2019 at 8:56 PM Martin Thomson <[hidden email]> wrote:

> You need to build a debug build with -DDEBUG. Disabling optimization is a
> different thing.
>
What command need option -DDEBUG?


>
> The default build with build.sh or make nss_build_all should be fine.
>
I always use `make nss_build_all` to build NSS.
Does that mean my build should already be a debug build?

Thanks!


>
> On Sat, 5 Jan. 2019, 11:40 John Jiang <[hidden email] wrote:
>
> > I had read that page. In fact, SSLDEBUG and SSLTRACE were used in my last
> > try.
> > My NSS was built with "BUILD_OPT=0", so I supposed it is a debug build.
> > How can I double-check this point?
> >
> > Thanks!
> >
> > On Sat, Jan 5, 2019 at 12:34 AM Kai Engert <[hidden email]> wrote:
> >
> > > Does this page help?
> > > You might need a debug build (i.e. build yourself with debugging
> > enabled).
> > >
> > > https://wiki.mozilla.org/NSS:Tracing
> > >
> > > Kai
> > >
> > > On 03.01.19 13:51, John Jiang wrote:
> > > > Just tried it, but looked not work.
> > > >
> > > > $ export SSLDEBUG=1
> > > > $ export SSLTRACE=127
> > > > $ tstclnt -v ...
> > > > I didn't get more logs.
> > >
> > --
> > dev-tech-crypto mailing list
> > [hidden email]
> > https://lists.mozilla.org/listinfo/dev-tech-crypto
> >
> --
> dev-tech-crypto mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
dev-tech-crypto mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-crypto