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

Question: How to enable debug logs? #583

Closed
freedom-foundation opened this issue Sep 3, 2024 · 3 comments
Closed

Question: How to enable debug logs? #583

freedom-foundation opened this issue Sep 3, 2024 · 3 comments

Comments

@freedom-foundation
Copy link

how to see debug info because when trying to connect to an ssl relay it reports SSL handshake exception. I need to see why it fails. I am guessing it is because certificates not trusted but the app really should be able to capture why it fails.
How to enable debug logs?

@oakkitten
Copy link
Collaborator

oakkitten commented Nov 16, 2024

Sorry for a late reply.

At the moment, you can see the logs in the Logcat. You'd have to enable developer options on the phone, install adb on your computer, connect the two devices together, and say adb logcat to view the logs.

We should definitely be displaying better error messages in the app itself. We use Toasts for this, which was “good enough” before but as these are limited to just two lines on recent Android versions, we should switch to Snackbars. I opened issue #587 regarding this.

@oakkitten oakkitten closed this as not planned Won't fix, can't repro, duplicate, stale Nov 16, 2024
@freedom-foundation
Copy link
Author

freedom-foundation commented Nov 16, 2024

At least you reply.

Sorry for a late reply.

Yeah and ATM for years logcat has been offlimits I haven't had root android since android 4.

At the moment, you can see the logs in the Logcat. You'd have to enable developer options on the phone, install adb on your computer, connect the two devices together, and say adb logcat to view the logs.

Yeah. All software would need security mindfulness. SSL is not done right anywhere. At times there is like a small simple but critical piece of info like a debug log that cannot be accessed so the entire purpose of all of it does fail. Like years of development by countless developers into nothing. With weechat it is one of those few softwares which is slightly intuitively better because it is the ONLY IRC client which is setup in such a way that you can secure your login. However, now that you bring me back to this it reminds me of the SSL / TLS bugs in weechat if you can't verify the server then securing your login credentials is not of much use. So I have pretty much forgot about weechat.

We should definitely be displaying better error messages in the app itself. We use Toasts for this, which was “good enough” before but as these are limited to just two lines on recent Android versions, we should switch to Snackbars. I opened issue #587 regarding this.

I'll take a look at #587 later.

@freedom-foundation
Copy link
Author

Kindof a note to self: all of SSL in weechat is broke and it would be better to remove it all. In the meantime you can use irssi with plain-connections only or maybe attack-dog IRC client. For about any of these apps to do SSL right and make it useful pretty much everything in openssl-tool should be availiable from within the app as an advanced security panel of some sort. WITHIN THE APP and apply to and against the ssl which is within the app ( not external libs).

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