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

Make connection message a NOTE for consistency #725

Merged
merged 1 commit into from
Jun 1, 2020

Conversation

jmartens
Copy link

@jmartens jmartens commented Jun 1, 2020

When disconnected a NOTE log entry is made in the log, when connected it just prints which seems inconsistent to me:

[2020-06-01T11:50:55] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD

	/home/jonathan/barrier/src/lib/net/SecureSocket.cpp,872
connected to server
[2020-06-01T11:52:43] INFO: entering screen

vs.

[2020-06-01T11:59:01] NOTE: disconnected from server
	/home/jonathan/barrier/src/lib/barrier/ClientApp.cpp,315

Since everything else logs with a timestamp I suggest changing this to NOTE as well for connection events being logged.

When disconnected a NOTE log entry is made in the log, when connected it just prints which seems inconsistent to me:

```
[2020-06-01T11:50:55] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD

	/home/jonathan/barrier/src/lib/net/SecureSocket.cpp,872
connected to server
[2020-06-01T11:52:43] INFO: entering screen
```
vs.
```
[2020-06-01T11:59:01] NOTE: disconnected from server
	/home/jonathan/barrier/src/lib/barrier/ClientApp.cpp,315
```
Since everything else logs with a timestamp I suggest changing this to NOTE as well for connection events being logged.
@shymega shymega self-requested a review June 1, 2020 13:42
Copy link

@shymega shymega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@shymega shymega merged commit 0a1f080 into debauchee:master Jun 1, 2020
@simons-public
Copy link

@p12tic @shymega @jmartens I think this might reintroduce the bugs in the GUI fixed by #664. I probably should have put a comment in the code there explaining why CLOG_PRINT was used instead of one of the other log levels.

Until the GUI uses the IPC to communicate status with the server or client I think this might need to stay as a print.

@p12tic
Copy link
Member

p12tic commented Jun 5, 2020

Indeed, we need a comment there explaining that this log message is much more important than it seems :-)

@simons-public
Copy link

@p12tic I'll put in a pull request when I get home and put a comment in there explaining the deviation from normal logging.

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

Successfully merging this pull request may close these issues.

4 participants