| Summary: | OTR fingerprint verification does not stay set to yes. | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | octo <octo777> |
| Component: | text-ui | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
octo
2016-03-28 02:12:28 UTC
Forgot to mention that I am using the plasma widget "Instant messaging" Well, it turns out that if while in the chat window with a contact, I go to Actions/OTR/Authenticate Contact , I verify the fingerprint and it does stay this way from then on. The way I was trying to do it earlier was to set it to "verified" in the known fingerprints section of Settings/Configure-Chat Application/ OTR. This would allow me to start a private session only while the chat window was open temporarily and would revert back to not verified if I close the chat and reopen it. I am not sure if this is normal functionality for it to not stick when changing it under settings, but I am happy now that I found what seems to be the correct method. Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |