Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server transaction logging #10

Closed
rmonk opened this issue May 9, 2016 · 1 comment
Closed

Server transaction logging #10

rmonk opened this issue May 9, 2016 · 1 comment

Comments

@rmonk
Copy link

rmonk commented May 9, 2016

If possible, can the server log when it performs a transaction for a client system? Something along the lines of "client IP X requested a transaction using protocol version Y"

This way, abusive/potentially malicious clients can be identified via log spam, and it can be used as a cross-check when nagios/etc does NOT report a reboot cycle, but the crypto server saw a decrypt request.

@npmccallum
Copy link
Contributor

This is now implemented. We now log messages like this:

127.0.0.1 GET /adv/default => 404 (tangd.c:63)
127.0.0.1 GET /adv => 200 (tangd.c:87)

This gives you the remote client, the HTTP method, the path, the response code and the location in the code where the response was issued from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants