This is called Unix Timestamp.

I just subtracted the first value from the second value, divided it by 60 and got 22,56

​@@Looki2000Yeah so 22 minutes and 34 seconds

@@renakunisaki If you're going to be technical (which this is the internet, so we definitely are), it's a timestamp, whose epoch is the unix epoch, namely the start of Jan 1st 1970 in whatever timezone you've arbitrarily set it to (typically UTC). Since we only care about the delta between the two timestamps (to produce a duration rather than a timestamp) the timezone doesn't matter as long as both timestamps share the same timezone (which they do) and even the epoch doesn't matter as once again it's only important if they differ. Subtracting the start from the stop gives us a value of 1,354 seconds between them, or 22 minutes and 34 seconds. Representing a specific point in time is a surprisingly difficult problem to solve and there are a ridiculous number of ways you can screw that up. Thankfully representing the difference between two points in time is significantly easier and much harder to screw up.

@@renakunisaki to be really technical since this is the internet, the unit is actually seconds.

Pretty much what I was going to post, u beat me to it, on a system that modern it would be effectively adding stuff that's not already built into the pch or extra of things already built into the pch (like usb)

I've seen some of those chips with IBM joystick, fan controller, and power monitoring as well.

​@absalomdraconis hmmm...yeah, I have/had a board (can't remember which one) and in the bios config it had a setting for joystick port, probably has a header somewhere for that...

@@robloxian1585 yeah, superIO is just where they stick literally anything and almost everything that they don't want to implement in discrete logic, so its a random crapshoot what can be in some of them lol

They are POSIX timestamps so the number of seconds since January 1, 1970 UTC

@@JordanWerthmanActually it is epoch time, more specifically Unix epoch time

balls hacked

@@LambdaMiscellaneous the enrichment center computers from the 90s h a c k e d

You can also just use a VGA port. The pin responsible for reading EDID uses SPI, and can write as well as read.

Hey, did it work for you? Wanted to make sure the password works for all of the MX2's

Yup, it worked for mine.

@@RedYoshiYT Do you happen to know if it also works for other types of ALLS? Say, the ALLS UX?

@@flottenheimer I don't own any other models than the MX2, so I'm not exactly sure.

@@RedYoshiYT Mine is on its way. Don't know the model/version yet. Just trying to prepare ;D ...

I came to the comments to see if anyone would say this. Hardware RAID is pointless in a home NAS in 2023 and honestly probably even in most enterprise use cases as well.

That's a very good point, I've still got the "mobo raid = hardware" misconception stuck in my head from somewhere

it's also totally useless if your drives are mismatched. You need to use freenas or something similar what that is the case.

Firstly, always a good idea to have unique passwords for every instance where one is required. I lax on things that are unimportant / don't access personal data, but otherwise I use an offline "password safe" and just generate a random password. So even if one is compromised, it doesn't open up anything else. But it's also worth noting that the password hash was backdoored here, and I mean, if an attacker has enough access to get into a database to steal password hashes, they've probably already compromised other data anyway.

On length alone, the time it takes to randomly bruteforce a password increases exponentially. Even with something as simple as a lowercase only password, increasing the length from 8 to 12 results in the total combinations possible going from 26^8 to 26^12. Even though the length is only +50% longer, the actual amount of combinations that have to be tried increases by the order of hundreds of thousands of times more. While it'd take only a few minutes to at worst an hour or so to crack the first password, the latter one would take upwards of 200 years to crack. Factor in the latter including uppercase letters, numbers, special characters, and so on, and the difference between the two goes from hundreds of thousands to hundreds of millions.

That 20 minutes means basically nothing btw. You can actually crack someone's password in less than a second if you get lucky enough and the length doesn't matter. A more accurate way of measuring it would have been to see how long it takes to generate every single password and then divide it in half.

Yeah, it's time to upgrade to 30+ character passwords, whether xkcd-style or random. More length = better

@@valshapedThat doesn’t really give you security. What gives you security is multi factor auth.

He tried it in full video, didnt work

I have my moments LOL. I'd love to get more technical with things but I'm worried it might shed off the less technical audience members. Luckily idgaf when it comes to this channel though

@@JonBringus yeah. I definitely subbed to this one after discovering it and after watching this. I like the more technical stuff but yeah. I totally get it. There is an audience for the technical stuff. It's just not a very big audience.

We worked on our videos at the same time, I actually spoke to them about it at LTX, it's all good

That's a terrible design. But in any case, this BIOS actually prompted that it was going to clear it. Also from the previous video, apparently clearing CMOS kept the password, so I'm guessing even if something weird like that happened, clearing CMOS would've put the stock password back in.

That's spooky damn, luckily if I really need to I can resolder back onto the chip and restore my original dump

@@CaptainSouthbird That clearly would not work. He could get the password hash by dumping the Flash (EEPROM) chip, so the password is stored in there. And at 1:49 you can see that it is in a region labelled "NVRAM" - non-volatile random access memory. That's how UEFI does it, there is no "CMOS" = battery-backed (S)RAM for storing non-volatile settings anymore like in the BIOSes of old, so you cannot reset it by taking out a battery or bridging a jumper. If you somehow managed to get the UEFI to reset the NVRAM, then it would most likely be wiped/cleared, meaning no password at all instead of a "stock password".

what laptop was it?

@@amarokorama wrong. Clearing the CMOS means clearing the user area. Which means the password does not go to empty, but rather it goes to the default rom password. Which for consumer motherboards is empty. But it is not the same thing, like in this board.

Be careful, if you are using the original Sega software. Your system propably uses Bitlocker with the key stored in the TPM chip. Image the Disk and try booting that image in a different machine or VM. If windows requests a Bitlocker recovery, you are on thin ice. If you mess with the hardware or BIOS it could trigger the TPM to no longer provide the disk encryption key. Bricking the system.

@@da1l616 I've already dupped the disk and it will boot on another platform but because specific I/O is missing it wont boot into the game.

Welp... So much for that idea. I've got a RingEdge2 PC in my Mai Mai. :( Its got a custom Sega mobo with only micro USB on it too. Ugh. Stuck with an non english version of Mai Mai I guess.

I'm pretty sure it's Fey's theme from Ace Attorney (turnabout sisters)

pi 3 is supreme, priced good and decent specs

I use the almighty CH341A

He tried that already. Either Sega had them disable that on this board, or the process is more complicated (such as it enabling a "OEM password" instead of clearing the user's password).

Actually yeah that would have been pretty smart & quick to do now that I think about it. That probably would have got me in no problem but I also really wanted to find the password because every single one of these Alls MX2 units shares a password. So now anybody that has one can use it.

I THINK that you could replace the default hash with your own hash that you know the password for, but like you said it's better to know the password so that everyone with an Alls MX2 has a password they can use too now

Iirc he tried that in the main channel video on this unit but I'm not entirely sure

That only works with older Lenovo laptops, because these store password in separate security chip from BIOS.

In case the bios has sega specific settings, and not wanting to risk corrupting anything if the bios flash failed

I did try that actually. I tried the F6 version BIOS for this identical board but it wouldn't boot up afterwards. Not sure why. I tried some consumer H310 boards as well but none of those BIOS's would let this thing boot up

you can use the password on any machine/board you find the wild, without having to solder to it.

@@JonBringus guess that's something we'll never know the answer too

If you mean the Cherry keyboard it's a MX 11900

Historically Sega has used the same bios password for all of their PC-based units, so every Alls MX2 SHOULD be using this password

@@JonBringus ah, interesting. I guess the bios password isn't that huge of a security thing. Probably just to prevent theft.

​@@Aeduo: More to prevent arcade owners from doing unscrupulous things, I think.

A lot of bitlocker'd partitions that I don't have the keys to

@@JonBringus :(

Virgin software raid user

Windows users do, because there isn't any great built in software RAID functionality, where linux has like 10 ways to have RAID. :p Macs have it built in too.

@@Aeduo Windows XP called, they want their software raid back.

Tried that it did not work for some reason