Bug 301697 - Wrong encryption state for mixed WEP connections on FreeBSD
Summary: Wrong encryption state for mixed WEP connections on FreeBSD
Alias: None
Product: knemo
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal (vote)
Target Milestone: ---
Assignee: John Stamp
Depends on:
Reported: 2012-06-12 00:20 UTC by Alberto Villa
Modified: 2018-10-29 22:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Fix to the issue. (690 bytes, patch)
2012-06-12 00:24 UTC, Alberto Villa

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Villa 2012-06-12 00:20:18 UTC
Wireless connections are marked as encrypted when WPA or WEP are on. In the WEP case, IEEE80211_WEP_ON is checked (which is deprecated by the way), excluding case where WEP connection accepts also unencrypted packets.

Reproducible: Always
Comment 1 Alberto Villa 2012-06-12 00:24:05 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).
Comment 2 John Stamp 2012-06-12 02:22:59 UTC
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
Comment 3 Alberto Villa 2012-06-12 02:28:40 UTC
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.
Comment 4 Andrew Crouthamel 2018-10-29 22:08:20 UTC
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.