| Summary: | Options to mitigate information leakage from default CTCP responses | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | gits1225 <gits1225> |
| Component: | protocol | Assignee: | Konversation Developers <konversation-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | glorfindelofrivendell, hein |
| Priority: | NOR | ||
| Version First Reported In: | 1.5-rc1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
gits1225
2013-06-27 12:52:32 UTC
You are able to customize CTCP response for VERSION but not for TIME and PING, I forgot to mention that in my earlier comment. CTCP TIME, OK, that's a potential information leak. CTCP PING, the information is from the sender, not your client. On Jun 27, 2013 9:36 AM, "Aby James" <gits1225@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=321673 > > --- Comment #1 from Aby James <gits1225@gmail.com> --- > You are able to customize CTCP response for VERSION but not for TIME and > PING, > I forgot to mention that in my earlier comment. > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > Konversation-devel mailing list > Konversation-devel@kde.org > https://mail.kde.org/mailman/listinfo/konversation-devel > Could this be implemented please? |