Skip to content

More verbose DEBUG logging #98

Open
@meg23

Description

@meg23

From [email protected] on January 14, 2010 20:48:05

I would like to see in general (i.e. not specific to any one version or
language) much more verbose "DEBUG" logging, particularly when it comes to
validating and encoding/escaping, so that one could for instance instruct a
development team who's using an adapter that I've built for them to turn it
to debug, re-run their tests, and send me the console output, where the
audit records are detailed enough to troubleshoot the security control in
question. For example, to output human-readable formatted bytes being
input/output. PKI toolkits, the better put-together ones, have something
similar, since debugging e.g. signatures can be equally painstaking.

Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=88

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions