#bug the computer tech

[bugthingsdaily]

today's bug thing are these ladybug computer mice!

[scipunk]

Paranoia 1.0 AKA One Point O (2004)

[quinowskie1]

imagine if your s/o was also your best friend that would be lit af

don't mind me im just a sucker for friends to lovers *clutches chest while on the floor*

[snoopylovessoup]

[its-stimsca]

Stimboard of Gordon Freeman from HLVRAI 👍

Center gif by @impossiblezeros :]

☢️ 📀 ☢️

📀 ☢️ 📀

☢️ 📀 ☢️

[st1mmywimmy]

Hello !! May i request a centipede and/or webcore themed Roger jones stimboard? I know some people aren't the biggest fan of bugs, so no pressure.

I'm aware you already made a rog stimboard but I just.. really like centipedes and computers. (And so does Roger! Or, well, maybe not the computer bit.)

⌨️webcore+centipede-themed roger stimboard🐛

HIM!!

x x x - x x - x x x

[futurebird]

ant technonogly

The disturbing thing about ant technology is it's all ants.

The fridge? It's an ant. Your tank? It's an ant. Your boat? It's you, and other ants. Your house? The walls are ants. Your weed control for your garden? Tiny ants? Your glue gun? It's an ant (a baby ant!)

So advanced high tech ants would have ant guns, and ant spaceships. Advanced ants would have ant computers for ants, made of ants. Advanced ants would have ants for storing data.

And ant bombs.

Wait! Those already exist!

[vioyume]

Ya think "Flower Journey" would get into controversy within the game world since the wasps are depicted as villains?

I spent too long playing this stupid flappy bird clone and I am forming stupid headcanons surrounding it.

You can probably make the same argument about the enemies in Mite Knight but they're more or less depicted as "mystical creatures".

Don't take this too seriously. I just thought it would be funny to have Flappy Bird be canceled.

[bugthingsdaily]

today's bug thing is this insect computer mouse!

[miltonlibassistantn1fan]

20+ // I sometimes forget to update my age on this site, I am an adult 🐜🐜🐜🖥️💻💾📱🐜🐜🐜

Edgar/Beep/Sar [present URL as a nickname is cool too, e.g milton] - it/he/they // objectum, probably some flavor of therian 🦖🐜🐛🪱🦠💌💌 profile image by @pigswithwings

PLAY THE TALOS PRINCIPLE

✅I'm a writer and beginner artist. My blog will be occasionally NSFW/suggestive. spam likes/reblogs are fine.

🕷️if i reblog something from you know that i am cheering for you even if we never talk🕷️✅✅✅✅✅

✅mutuals can message me or rip me open for parts.

❌DNI/DNF zoos, whatever other weird shit is floating around, people that love drama for some reason. don't follow me if you think being objectum is gross or w/e. ❌

Important links below 🪕misc tags will be added to this post so you can poke them and look at stuff

art that is mine look at my art boy // original text post tag // comfort character tag // my writing tag

Blinkies and boxes and other cool stuff under the cut

Things I love --- 17776, kirby, ULTRAKILL, hollow knight, postal series, will add other stuff

[ CREDITS CREDITS in order, labratgurlz zouserboxes, y2khaos crowcryptid ]

[s1llybug-old]

compuper :]

[byruit]

In the late 1990s, IBM established Year 2000 Conversion Centers to tackle the Y2K problem, where many computer systems could fail due to date misinterpretation.

These centers helped organizations identify and fix Y2K issues, offering services like code conversion, testing, project management, and training.

With a global reach, IBM collaborated with tech companies, industry groups, and governments to ensure systems were updated and ready for the new millennium.

Their efforts successfully mitigated potential disruptions and set a precedent for managing large-scale IT challenges.

[cerulity]

Common Things Vulnerable to Y2K38 (+ Explanation)

I want to compile a list of things I find that are vulnerable to the Y2K38 bug. If you find any I don't know about, I can add them to the list. But first, an explanation...

What is Y2K38?

For those that aren't aware, past January 19, 2038 at 3:14:07 UTC (2038-01-19T03:14:07Z), the number of seconds since midnight of January 1, 1970 (1970-01-01T00:00:00Z) will surpass 2^31 - 1.

So what are the implications of this? It has to do with how computers store time.

The Unix epoch is defined as the number of seconds since January 1, 1970, and this is universal to both Unix and Windows systems (so virtually every single computer that doesn't have a homemade operating system). The issue is what specific types of numbers are used to store the epoch.

There are two properties to an integer type: size and sign. The size dictates how many bits a number can hold, and the sign dictates whether or not the integer can store negative numbers. If the number is unsigned, it will be able to store numbers ranging from zero to 2^n - 1, where n is the size of the integer in bits. This means that an 8-bit unsigned number can hold numbers ranging from 0 to 255, because 2^8 - 1 is 255. If a number is signed, the positive range is cut in half. Signed numbers range from -2^(n - 1) to 2^(n - 1) - 1. This means that an 8-bit signed integer can hold numbers ranging from -128 to 127, as -2^7 is -128, and 2^7 - 1 is 127. As integers are used to store the Unix epoch, this means that the epoch is limited to the range of the integer type you use to store it.

If you decide to use a 32-bit signed integer to store the Unix epoch, then once the epoch reaches 2^31 - 1 (which is the upper limit of 32-bit signed integers and is around 2.1 billion), the epoch won't be able to increase anymore. So what happens when we try to increase it anyways? We get an integer overflow.

Due to how CPUs add numbers together, when the result of an operation is larger than the range of the integer type, the result is wrapped around. For example, if you have the number 127 in an 8-bit signed integer, adding one will wrap around to -128! This is a problem for the epoch, because now, instead of storing 2.1 billion seconds past January 1, 1970, it will now be storing 2.1 billion seconds before 1970, which goes all the way back to December 1901!

So why not just use a bigger number? Well, it's not really that simple. There has been an effort to switch over to 64-bit integers, which has an overwhelmingly generous range of around 21 times the estimated age of the universe. However, there are some systems that just can't change or haven't changed for a variety of reasons, and this is what the list will be about. There are two main causes for the Y2K38 bug, and most vulnerabilities stem from them:

32-bit representation of of time_t: time_t is the integer type that time is stored in. When a C program calls the time() function, it will receive a time_t. If time_t is 32-bits long, then the time() function will be vulnerable.

Downcasting the result of time(): There's a pattern in programming I like to call "int-defaultness". C's primitive types are not named with sizes. Instead, they are called 'char', 'short', 'int', and 'long'. These types are standardised to be at least 8 bits, 16 bits, 32 bits, and 64 bits respectively, but most platforms just use those sizes exactly. Usually, you would use exact-sized types like int16_t, uint64_t, and so on, or if it's a function like time(), you would use time_t. However, it is a common pattern to default to int as an integer type, and someone who isn't careful may just convert the result of the time() function into an int. This is known as downcasting, which is the conversion from one integer type to a smaller one. Regardless of whether or not time_t is 32 bits or 64 bits, this downcast will always convert the time to 32 bits, and the overflow behaviour will apply, leaving PHP vulnerable.

As you can see, the time() function is the root cause of the bug, and due to its popularity, usages and mimics of time() can be left vulnerable.

So, without further ado, here is...

The List of Vulnerabilities

PHP time() function: PHP has a time() function that acts very similar to C's, and if the size of a PHP int is 32 bits, PHP is left vulnerable.

pcap file format: The pcap file format (used by libpcap, which is used by utilities like tcpdump and Wireshark) is a format for storing captured packets, and the specification states that the timestamps of packets must stored in a 32-bit unsigned integer. Luckily, since it is unsigned, this will overflow in the year 2106, but there is still some vulnerability here. The PcapNG file format uses 64-bit timestamps, which prevents the vulnerability.

Embedded systems: Smaller computers have a tendency towards lower bit-widths, and 32 bits is common. Embedded systems control things like radios, elevators, GPSes, and more things that don't require heaps of computation power. These systems commonly define time_t to be 32 bits, making them vulnerable.

[thepastisalreadywritten]

[tillman]

sorry if this is a silly question but whats the circle in front of finch’s face? live the design btw!

finch is actually a beekeeper ! well. small gears. small bee gears that produce a Lot of blood that allows leech to have some sort of sway over them. they happened into this position while helping out a small town and ended up becoming their silent protector- so the beekeeper outfit come half as a needed disguise to keep them from knowing they kind of technically a gear by blood volume ... but they ended up enjoying it. i honestly just am too lazy to draw them wearing it and typically simplify the shit out of it for fun LOL.

its inspired by a weird mix of y2k bright colors and glossy sheen and medieval beekeeping masks hehe.

[luetta]

idk if people on tumblr know about this but a cybersecurity software called crowdstrike just did what is probably the single biggest fuck up in any sector in the past 10 years. it's monumentally bad. literally the most horror-inducing nightmare scenario for a tech company.

some info, crowdstrike is essentially an antivirus software for enterprises. which means normal laypeople cant really get it, they're for businesses and organisations and important stuff.

so, on a friday evening (it of course wasnt friday everywhere but it was friday evening in oceania which is where it first started causing damage due to europe and na being asleep), crowdstrike pushed out an update to their windows users that caused a bug.

before i get into what the bug is, know that friday evening is the worst possible time to do this because people are going home. the weekend is starting. offices dont have people in them. this is just one of many perfectly placed failures in the rube goldburg machine of crowdstrike. there's a reason friday is called 'dont push to live friday' or more to the point 'dont fuck it up friday'

so, at 3pm at friday, an update comes rolling into crowdstrike users which is automatically implemented. this update immediately causes the computer to blue screen of death. very very bad. but it's not simply a 'you need to restart' crash, because the computer then gets stuck into a boot loop.

this is the worst possible thing because, in a boot loop state, a computer is never really able to get to a point where it can do anything. like download a fix. so there is nothing crowdstrike can do to remedy this death update anymore. it is now left to the end users.

it was pretty quickly identified what the problem was. you had to boot it in safe mode, and a very small file needed to be deleted. or you could just rename crowdstrike to something else so windows never attempts to use it.

it's a fairly easy fix in the grand scheme of things, but the issue is that it is effecting enterprises. which can have a looooot of computers. in many different locations. so an IT person would need to manually fix hundreds of computers, sometimes in whole other cities and perhaps even other countries if theyre big enough.

another fuck up crowdstrike did was they did not stagger the update, so they could catch any mistakes before they wrecked havoc. (and also how how HOW do you not catch this before deploying it. this isn't a code oopsie this is a complete failure of quality ensurance that probably permeates the whole company to not realise their update was an instant kill). they rolled it out to everyone of their clients in the world at the same time.

and this seems pretty hilarious on the surface. i was havin a good chuckle as eftpos went down in the store i was working at, chaos was definitely ensuring lmao. im in aus, and banking was literally down nationwide.

but then you start hearing about the entire country's planes being grounded because the airport's computers are bricked. and hospitals having no computers anymore. emergency call centres crashing. and you realised that, wow. crowdstrike just killed people probably. this is literally the worst thing possible for a company like this to do.

crowdstrike was kinda on the come up too, they were starting to become a big name in the tech world as a new face. but that has definitely vanished now. to fuck up at this many places, is almost extremely impressive. its hard to even think of a comparable fuckup.

a friday evening simultaneous rollout boot loop is a phrase that haunts IT people in their darkest hours. it's the monster that drags people down into the swamp. it's the big bag in the horror movie. it's the end of the road. and for crowdstrike, that reaper of souls just knocked on their doorstep.