As you can see below, my letter to Lou Dobbs to enlighten him re how software can be corrupted itself was corrupted (possibly). I've never seen a returned email failure like this one. But skip over the email message garbage and you too can be enlightened re software corruption, although just a highlight and just a small fraction of the possibilities.
--------------------------------------------------------------------------------------------------------------------- Forwarded Message --------
| Subject: | failure notice |
|---|---|
| Date: | 9 Nov 2020 23:25:25 -0000 |
| From: | MAILER-DAEMON@mail.hostingplatform.com |
| To:xxxxxx | [privacy change] |
Hi. This is the qmail-send program at mail.hostingplatform.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<lou@loudobbstonight.com>: user is over quota
----------------------------------------- The actual letter to Lou --------------------
Mr. Dobbs,
I am retired now but took my Computer Science degree to IBM in 1974 where I started in operation system development, design, testing, etc. I spent 23 years with IBM through system engineer, marketing, management, and finally I/T Mgt. and Process Consulting. I'd like to share some EASY ways software can be corrupted:
1. The software provider could have course written code that allowed modification, e.g., making it take a non normal but desired path based on human input when starting or when already running. Likewise, any hacker or hacker who implanted a virus could make a program behave the way they want. Think Ransomware!
2. Given above, it is simple code to include an "IF" condition that keys on either a human command/input parameter OR checks the computer date and time to either react the way they want it to after that date/time or even between a certain time period. Here are a few scenarios of corruption possibilities:
 a. Code already exists from provider, either by them knowingly, or by an employee with authorization to manage the code, or by a hacker who implants a virus (code) that asks "is it the day after the day normal election results are completed? If so, then count every ballot read as Democratic.
b. Same as a. above but do so only for a period of 4 hours then go back to normal.
c. Instead of a time trigger, wait until a specific batch of ballots are read, but which are identified uniquely to be counted as all Democratic, e.g., name the batch MAIL-INs so the corrupt code is alerted to take the Democratic path only.
REMEMBER. It only takes ONE "IF" statement/Command in the code along with ONE "GOTO" Democratic path. Very little code and that could be hard-coded or hacked into the provided software.
Things a forensic computer science expert could do to determine corruption:
1. Confiscate the original code from the provider and compare it (date, version, build, size, etc.) and check it against the code running if it wasn't already corruptly replaced. A difference immediately indicates some corruption.
2. Every Operating System has some type of Logging of events, such as a program starting, a modification to a running programs, a program stopping that alo reports the version/build/date/size. These need to be examined.
3. Run a sample batch of ballots, say 50-50 expected, on a computer who date is set for election day and day after, and then various days after that. All results should match. If not, there is date/time specific corruption code present.
4. Follow on to 3. is to determine if all strange behaviors in counts started at the same date/time or withing the same period. Another indication that hacked/corrupted code is present.
I can think of even more I would look at to quickly identify corrupt code. Surely SOMEBODY is doing this, I hope. I just wanted to bring your knowledge level up to completely understand HOW code can be corrupted. Please us this to question the election results and get the SOMEBODIES busy.
A second and even more important thought beyond just the election corruption: I am astonished the Republicans can't find a Champion who wants to fix the Democratic indoctrination of people at educational institutes. We cannot expect even 50% of the voting population to understand the economy. Thanks for trying every day. Your preaching to me for example yield no more than I already know. It's the other 50% who never tune in that will never get it. Trump's biggest failure was antagonizing those 50% and all it's leaders. All great things he has done for us has gone unnoticed, or should I say ignored, by the clueless. Yes, I am angry that he took such a debasing position. Where do we go from here?
And here is the most simplistic kicker I think that is driving people to the Democratic Party: It's NAME! The ignorant have no clue that America was a REPUBLIC and they incorrectly associate DEMOCRACY to the party name Democratic. Not once have I ever heard anybody explain this to the people. Surely, the indoctrination may even teach this falsehood! America needs to rename the parties maybe to Liberal and Conservatives, or A and B, or Tiger and Bears. We need to STOP using Democrats -- maybe change it to Socialists!
Lou, keep up the good work. I know your lessons do help those listening. However, behind the scene we need to find the Champion who i going to be relentless in understanding the issues and changing the direction and education. I started blogging during the Obama years re all the corruption and measures to correct it -- all gone to waste for those 8 years and 4 more. We the People will be no more than dirt in another 12 years. Unfortunately, I might still be around since my mom lived until 98!
Please stick to your guns Lou!
No comments:
Post a Comment