Re: WYF!
6502 assembly could be programmed from the BASIC UI.
73 publicly visible posts • joined 3 Jan 2019
Managers are divided between those who refuse to believe a bug exists even when it was discovered years earlier by a member of their own team - that the manager has spoken to but insists that he knows better than technical staff
Or the kind that believes bug reports such as red hat rpc still contains a flaw fixed in 1998 just because the version number shown over the network is still 1.2 .
Neither one is curious enough to ask about the truth or be any more satisfied with better conditions than you get by doing nothing. This ensures that nothing will be done except useless things because something must be done
These are real examples from work and people with names omitted.
Long ago somewhere in this galaxy there may have been someone who tinkered with the inside of a PC so much he got to leaving the screws undone and the case open a few centimetres. Then there was contact from a near neighbour (who had not seen indoors at this place) complaining "You're running a PC with the case off which interferes with TV signal and is illegal". The case went back on and there was no more complaint.
I used to report port scans and intrusion attempts ... even cataloged the preferred contact method (email/web form * groups/single items) for a bunch of ISPs and automated the reports (with a rate limit).
The most annoying was my own ISP since they couldn't reliably read logs (bsd pf logs in tcpdump format) and often contacted me claiming I was the source of the scans I'd complained about.
I had a luser claim that my s/w changed his Solaris hostname to "-a". Puzzled by this since I'd been running it on Solaris for a long time and knew it never changed the hostname, I invited him to look in root's shell history for "hostname -a" where perhaps "uname -a" was intended.
I never heard back.
I (and Kevin) had to deal with a situation in the early 1990s where the culprit (Carl) had been the last person to leave on Friday (and by the time we arrived on Monday was abroad on leave). He'd left some sort of unfinished reformat and reinstall job without so much as a note about how far he'd got and what was left to do.
During his holiday someone phoned for him and when I said he was away they asked "Oh! How do you manage without him?".
> phony invoices that each of the tech giants thought were for real purchases
Years ago I worked at a place that tried to pay invoices whether they were due or not. The drone I spoke to on one of these occasions was panicking that "they might sue us" while I was telling him the cancellation I had in the correspondence file would keep us safe if they did.
I found a situation where a password could not be changed; even by root using 'passwd -r files luser'.
The line in /etc/passwd was there but the passwd program was not reading it. Enter truss .. /bin/passwd was quitting before reading the whole file which meant a problem in the file. pwck pointed out wrong number of fields.
And somebody's edit had left a blank line mid-file resulting in later lines not being used.
do { ... } while(0) was a tool taught me* in the 1990s for use in C macros.
When you have your code:
if (x) frobulate;
you don't need {} after the if even when frobulate is #define'd as multiple statements of something.
* by the pdksh maintainer Michael R?? er, web search suggests Rendell
> warning for anyone ever tempted to insert witty error messages into their code
sudo has an option for "insults" (strange sayings emitted when you enter a wrong password). I maintained sudo for a while in a company which meant download/compile/package when there was a new version. There were a few people so alarmed by the "insults" that they made helpdesk calls to people who didn't know what they were and didn't know how to find out about them. In later releases I made sure the insults were turned off.
examples here: https://grayson.sh/blogs/viewing-and-creating-custom-insults-for-sudo
Years ago there was a debate in the newspaper about pay in public v private sectors. Someone defended his public sector pay because of the amount of money he managed (i.e. spent). Another writer said spending money is easy and the hard work in the private sector is earning the profit.
Your experience is not complete until your boss personally tells you that an unpatched bug does not even exist . This is a bug that you discovered and reported to the vendor 9 years earlier and (after testing the patch) sent a description to a security mailing list that's archived on the web.