I did a similar thing at a place I worked at. I order to go over the heads of insane management and actually get work done, rather than just have sugar cubes counted at me all day, I created an administrator account with the username of .

Not blank. The character " ".

What, you can't see it? It's a non-breaking space. You can type one (on a Windows machine) by holding Alt and pressing 0160 on your number pad.

A shocking amount of "enterprise" software is not equipped to handle a non-breaking space, and will not detect it as a naughty character nor treat it as whitespace -- which is probably what should happen. So what you get is an invisible user, which is also helpfully sorted to the bottom of lists where no one will notice it, because its numerical index in character space is well below all the typical letters and numbers that'll be used for user account names. Does your software require a user name of greater-than-one character length? No problem, just type in a whole bunch of them.

Non breaking spaces can also mess with the formatting of systems with user-facing text input that'll regurgitate it later. Like, oh, forums. Or comment threads. Like this one. Even those that are "smart" and attempt to collapse repeated whitespaces into a single line break.

For instance.

Yeah, that sort of thing.
- I was burned afoul by a former admin who, instead of diagnosing why a mail service was failing, labeled a script as a /etc/cron.d file entry as "..." (three dots) which, unless you were careful, you'd never notice in an "ls " listing casually. The cron job ran a script with a similar name which he ran once every 5 minutes. It would launch the mail service, but simultaneous services were not allowed to run on the same box, so if it was running, nothing would happen, although this later explained hundreds of "[program] service is already running" errors in our logs. It was every 5 minutes because our solarwinds check would only notice if the service had been down for 5 minutes. The reason why the service was crashing was later fixed in a patch, but nobody knew about this little "helper" script for years.
  
  Until one day, we had a service failover from primary to backup. Normally, we had two mail servers servers behind a load balancer. It would serve only the IP that was reporting as up. Before, we manually disabled the other network port, but this time, that step was forgotten, so BOTH IPs were listening. We shut down the primary mail service, but after 5 minutes, it came back up. The mail software would sync all the mail from one server to the other (like primary to backup, or reversed, but one way only). With both up, the load balancer just sent traffic to a random one.
  
  So now, both IPs received and sent mail, along with web interface users could use. But now, with mail going to both, it created mass confusion, and the mailbox sync was copying from backup to primary. Mail would appear and disappear randomly, and if it disappeared, it was because backup was syncing to primary. It was slow, and the first people to notice were the scant IMAP customers over the next several days. Those customers were always complaining because they had old and cranky systems, and our weekend customer service just told them to wait until Monday. But then more and more POP3 customers started to notice, and after 5 days had passed, we figured out what had happened. And we only did Netbackups every week, so now thousands of legitimate emails were lost for good over 3000 customers. A lot of them were lawyers.
  
  Oof.
  
  I was shadow IT for a project and asked IT to design this special unconventional thing which of course they wouldn't. So I made this little embedded linux device to take care of it. Gave them the design and steps I made and all that. They were like "nah" so I told them to give me admin on their file server and switch and I'd just do it myself. So they did (lol?).
  
  I had to create a service account, so instead of just having the system account do it on their file server because I figured that wouldn't be OK. I asked them how do I properly get a service account approved and they passed me to Cyber who had me submit a user request. It got denied because it didn't have a signed user agreement or a Sec+ or similar cert......
  
  So I created a word doc that said "I am not a real person and therefore cannot sign any contracts. I am just software man." and exported it to PDF and named it the same name of the agreement file name. Did the same for the cert. They approved it.
  
  Then nobody ever created the account because IT's helpdesk couldn't figure out how to do it. I think it was more that they probably didn't have an OU structure properly set up so they wanted some architect or something to weigh in.
  
  Anyway, I just let System do it because, well I had been waiting months at that point. The service account probably still doesn't exist in AD. They then took my admin privs away and got credit from upper management for solving this odd problem that my stuff took care of.
  
  Eventually they needed a more robust solution and also in a few more places since it worked well but they started slamming it a bit too hard with data. They wanted to just keep giving me specific rights and then take them away when I was done but also submit paperwork every single time to them to do it.
  
  Apparently, I burnt bridges when I said "nah" as a Reply to All when they told me that. But who cares to have a bridge to nowhere anyway? As far as I know (since I still occasionally get a technical question about it) my little guy is still chugging away today, though I've moved on since then.
  
  I hope to be this based.
  
  A lot of them were lawyers.
  
  I'm not seeing the downside here
  
  Sometimes lawyers work on things like protecting the environment, civil rights, prosecuting fraudsters, and exonerating innocent prisoners. But lawyers are also subject to deadlines that they don't set and that could be set at the last minute. And sometimes, they can only be aware of that deadline if they receive the email with that information. So, in theory, you could have major repercussions for someone because their lawyer missed an email.
  
  Did those lawyers not also have a separate archiving service like they should have?
  
  Actual question: how would they archive something they never received?
  
  That's... not how load balancing is supposed to be done...
- I enjoy that the character that can break a lot of things is called the "non-breaking space".
-  
  
  Nice try, HTML hacker.
  
  ? I'm using Mobile
  
  I just copied the markdown and stuck it in a code block to make it visible.
  
  I was joking lol
- Is this what chaotic good looks like?
- I only know about it because it was a popular way to make an invisible folder no the desktop, teens loved it for stuff.
- I did a lot of web scrapping this week at work and it's looks like that character is used a lot on XPaths and CSS selectors. I only noticed it because VS Code put a yellow box around the character and give you a warning that that character is not a whitespace.
- I love this
- I can't tell if you're starting a cult. Whatever, I'm in...
- Where did you make the admin account if you don't mind me asking. You saying you made a local admin account or maybe an admin account in AD?
- The software developer in me hates you. You're not wrong but still 😡
- Kbin didn't feel like translating your example.
- That's interesting but what I really want to know is what kind of evil things you did with the invisible superpower
- Connect for Lemmy renders these as
  
  So it's at least acknowledging that there's something there.
- Gonna read Terry tonight 🍻
- Its rendering as a spacw for me on eternity lol. U can also put it in the middle of words to make word count heigher than it should be lol.
  
  It is a space, so it's correct that it shows up. Non-breaking means that something like line wrap won't happen.
  
  Putting it in the middle of a word will show up. That trick must've been a different character.
  
  Ohh though u where talking about zero width spaces they are also fun.

You've viewed 63 comments.