Tiny Core Base > TCB Bugs
TinyCore64 14.0 wifi.sh failures
CentralWare:
Theoretically, if we're encapsulating the entire string in quotes, spaces "s h o u l d" be accounted for. (?)
Asterisks -- I've never seen nor used one in an ID, but it's "allowed" and more times than not, escape \* is going to be needed.
: and / are more Win based screw-ups so they're likely able to be disregarded here, but semi/colon is a worthwhile router test "just cuz"
as I think our baby firewalls allow almost any/everything - including illegals...
SSID: asdf\qwer:$5%+[] was permitted on a WatchGard XTM series AND a Cisco 3600 (up-stream from it) didn't bitc... complain about it :o
Okay, add $ and \ to our hit-list; to my dazed look the above SSID is visible on this Win'Nix desktop
* $ \ & and space encapsulation should cover MOST of the bases; those others who just HAVE to create identities which fall within the realm of illegals... shouldn't be our problem
Rich:
Hi CentralWare
--- Quote from: CentralWare on February 18, 2024, 11:42:47 AM --- ... * $ \ & and space encapsulation should cover MOST of the bases; those others who just HAVE to create identities which fall within the realm of illegals... shouldn't be our problem
--- End quote ---
Are you saying we should accommodate the illegal $ and \ characters?
CentralWare:
Yes (I would, simply because I can CREATE an SSID with them on certain hardware and that they actually WORK, even though standards say
they're illegal and the few Tenda, TP-Link, D-Link and EnGenius routers which were tested when I sent that update agree that they're illegal
and have the user "try again" -- but that's not saying everyone else does - or that other models of the same brands do as well.)
$ is a Linux problem regardless -- not as much on Win (used to $HIDE directories, otherwise can be used for most anything else)
* is a Linux problem and a completely different Win problem (Win = Wildcard - just "illegal" period, so SSID="MY*PRECIOUS" choked
on Win11 test a few minutes ago just responding "Cannot connect to network" and that's it.)
\ is a Linux issue, not as much on Win (mainly batch issues from yester-year)
& is a Linux only thang (that I'm aware of) SSID="Tom & Jerry" worked out of the box in both directions wunder win10/win11;
CentOS must have encountered this previously as it's already prepared for it. Debian... I think my image is "borked"; doesn't act right.
patrikg:
Funny facts.
I have setup my IPhone with the name of :) as emoji.
And when i setup my phone with internet sharing, it shares my phone with ssid :) as emoji.
And when a search a little of this topic on the web, i can find that the standard don't say so much of what chars are correct to use.
So you can even use some chars that are difficult to type in from ordinary keyboard.
Have heard about some have tried to use $s $d, so even leak and break the phones, with seen this ssid's.
I think lots of implenentations have difficult to use chars that are not ascii.
CentralWare:
--- Quote from: patrikg on February 18, 2024, 04:05:48 PM ---I think lots of implenentations have difficult to use chars that are not ascii.
--- End quote ---
Yes, but the problem lies within the first half of the ASCII table where certain characters "mean something"
to the underlying operating system that's trying to connect to it, especially shells and interpreters.
For example, the ° symbol (Degrees) is easy to implement into a router. It works in both directions,
but may be a pain to input manually and almost impossible for hardware like printers to connect without
using WPS. This can be a benefit for security - or a liability for sanity!
The $ (Dollar Sign) on the other hand means Currency to most people... but to a Linux based computer,
it means Variable in many cases thus why it's considered a Reserved character and must be "Escaped" for
the computer to see it as a normal character.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version