WiFi pwd with special characters

Networking WiFi
1

When setting a password for a WiFi connection (WPA2) that ends with “y{?/”, the entry in the “Wireless Client Configuration” area seems malformed.

Those four characters “y{?/” are present in the Priority column instead of a number, like with the other entries that are configured.

So far I’ve not been able to connect to the WiFi in question so I’m guessing that this particular WiFi password is breaking the configuration in IPFire.

Any help would be appreciated.

2

Was the character in the password just before “y{?/” a comma?

Many things are in CSV format in IPFire so a comma is taken as being the separation of entries.

If you did have a comma in the password, the simplest option you have is to remove it from the password.

If it is not a comma, what was the character immediately before?

3

You are absolutely correct, there is a comma preceding that sequence of characters.
Sadly it’s a password that I don’t have access to change so I guess we’re stuck for now.
Thank you for the insight!

4

It would be worthwhile to raise a bug on that.

The same thing was an issue with the PSK for the IPSec connection and it was raised as a bug and the password encoding was changed to base64 encoding.

Similar option should be able to be used here, although it would not be able to get implemented until Core Update 191 at the earliest. Raising it as a bug ensures it is recorded and will get addressed when resources are available.

See
https://www.ipfire.org/docs/devel/bugzilla
for details of how to raise a bug.
Your IPFire People email and password will act as your IPFire Bugzilla login credentials.

1 Like
6

That may also be valid for the WLAN addon although I don’t know if that page does or does not have base64 encoding applied to the password entry or not. If base64 encoding has been used then a comma can be used as it is encoded to a different character.
If base64 encoding has not been used then a comma would also give a problem with the WLAN addon.

This post was related to the Wireless Client option for the Red Connection, instead of using a ethernet cable connection.

7

I’ve submitted a bug but I’m unsure if I picked the correct component:
https://bugzilla.ipfire.org/show_bug.cgi?id=13792

2 Likes
8

For IPFire2.x then the component is always - - . A named component is only used with IPFire3.x

9

OK, so I deleted that note.

10

I amended the bug report to - -.
Thank you for the help!

2 Likes