| Summary: | Wrong encryption state for mixed WEP connections on FreeBSD | ||
|---|---|---|---|
| Product: | [Applications] knemo | Reporter: | Alberto Villa <avilla> |
| Component: | general | Assignee: | John Stamp <jstamp> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Fix to the issue. | ||
|
Description
Alberto Villa
2012-06-12 00:20:18 UTC
Created attachment 71748 [details]
Fix to the issue.
The attached patch uses the (newer) IEEE80211_IOC_PRIVACY request to mark the correct encryption state, which switches to "active" for WEP connections accepting also unencrypted packets (as done in Linux backend).
SVN commit 1299928 by jstamp: Report correct encryption state on FreeBSD This fixes a problem when KNemo reports a connection as encrypted if a WEP connection also accepts unencrypted packets. Patch contributed by Alberto Villa. M +2 -7 bsdbackend.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1299928 Actually, it does the opposite. Previous to this commit, such a connection would have been reported as non-encrypted. Now it's marked as encrypted. The logic was chosen by checking Linux backend, reading emails all over the Internet, and checking FreeBSD man pages. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug. |