Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
Posted on 19-07-04, 20:18 in I have yet to have never seen it all.
Dinosaur

Post: #421 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by sureanem
-rw-r--r--  1 tomman tomman 2418 oct 26  2001 seleccionaidioma.php
-rw-r--r-- 1 tomman tomman 3157 oct 26 2001 seleccionaidioma.php.racista

So, uh, how do these two files differ?


Apparently the "racist" version hides the Galician entry by default:
            <table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td>
<div align="center"><a href="es/centroportada.php" class="textotitular">Castellano
- </a><a href="javascript:;" class="textotitular" onClick="MM_swapImage('enanillo','','es/images/galego.gif',1)">[+]</a></div>
</td>
<td>
<div align="center"><a href="en/centroportada.php" class="textotitular">English</a></div>
</td>
</tr>
<tr>
<td align="center"><a href="gl/centroportada.php"><img src="es/images/enano.gif" width="71" height="10" name="enanillo" border="0"></a></td>
<td> </td>
</tr>
</table>
<br>


The regular one just shows all languages at once:
            <table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td>
<div align="center"><a href="es/centroportada.php" class="textotitular">Castellano</a></div>
</td>
<td>
<div align="center"><a href="en/centroportada.php" class="textotitular">English</a></div>
</td>
<td>
<div align="center"><a href="gl/centroportada.php" class="textotitular">Galego</a></div>
</td>
</tr>
</table>


As a outsider, I don't get it. But when you consider how delicate have been relationships between Spainards and Galicians through history you may get it. Or not.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-05, 13:23 in I have yet to have never seen it all.
Dinosaur

Post: #422 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by CaptainJistuce
https://www.youtube.com/watch?v=iLsdlNrLPxQ
Guy gets an old Macintosh 512 that doesn't work. Goes to open it for repair, notices it is strangely heavy. Opens it up and a bigass full-height 5.25" hard drive is staring him in the face from behind the case of this "unexpandable" "floppy-only" system.

Turns out the company that made this hard disk controller(called a Hyperdrive board, and I love the name) decided to give Steve Jobs the finger in the most blatant way possible(other than actually etching an illustration of the bird onto the board).
"You say your computer is unexpandable and unmodifiable? There's no expansion bus and it shall be thrown away when it ceases to meet our needs? Well, all the address and data lines end at the CPU, so we're just gonna clip a ribbon cable on top of it and MAKE an expansion bus for our hard disk controller. We think Wozniak would approve. Also, we're taping a fan into this air vent. It isn't even fanless anymore. "

Related reading: http://www.folklore.org/StoryView.py?project=Macintosh&story=Diagnostic_Port.txt&sortOrder=Sort+by+Date

I wonder if Burrell Smith would approve (and if he actually pissed over Jobs' grave after he died)

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-06, 23:35 in I still HATE smartdevices
Dinosaur

Post: #423 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
The Blu Dash X (now in the hands of its new owner, $COUSIN's father) came back to me, in the same unbootable status I got it last time. Redownloaded system partition, phone booted again, and all data and crapps were intact! But then... phone was behaving erratically after a while. Magisk was losing root status after a while, random Chrome windows were opening at random (some of them with unknown URLs). After trying to update Magisk, phone only booted to TWRP (recovery). Uh-oh...

Reflashing the FULL image did nothing, the bastard piece of shit only booted to recovery! Finally... I pulled the SIM card out, reflashed it once more, and BOOM! Boot again! Now I get to deal with Android's FRP sekuritah theater. Long short story: if you ever steal phones forget your Google password, and have a Mediatek-based phone, bypassing FRP is trivial:
https://www.getdroidtips.com/bypass-frp-google-mediatek-sp-flash-tool/
https://www.academia.edu/38242529/How_To_Reset_FRP_on_MediaTek_Phones.pdf
If you've flashed your phone at least once, you already have the tools for it. Thanks Mediatek!

Now I get another chance to brick this bastard.

$MOM's Allcrapper is crapping its pants as usual. *yawn*
Without reliable Internet access for more than 5 minutes a day, it's not even worth to take a look. Backup Whatsapp shit to a SD card and pray.

Also: fuuuuuuuuuuuuck you Silly Valley assholes that are trying to kill Bluetooth OBEX as a standards-compliant way to share files between devices. In the era of dumbphones (and assuming your carrier didn't crippled OBEX THAT'S WITH YOU VERIZON!), sending files between phones was dead simple: enable Bluetooth on both devices, ensure both are visible, open photo/sound/video, find the "Send via Bluetooth" command on your OEM UI, do it, done. But nope, that's not how millenials share cat memes nowadays! You're supposed to use WhatsFuckingApp or whatever Internet-required data silo just to beam a picture between two phones that are only one meter apart!

Yes, Android still does OBEX. But on my Z835, sometimes the phone insists that a pairing must be established first for no good reason at all. And on other phones, like $COUSIN's Samturd Galaxy J4, figuring out where Bluetooth-received files are located is an exercise in frustration. Also, I can't believe Samturds can't render SVG files by default (none of the Samturd built-ins can open them), yet my shittyass ZTE with Simple Gallery can do! This really gets in the way when you're trying to teach someone how to get your Inkscape art out of your PC and into your Instagranolas feeds.

God damn it, my head aches every single time I'm near of a smarturd :/

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Dinosaur

Post: #424 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Buster is now the new sexy hotness. Grab while it is not (too) stale now!

This time I will read the release notes!
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html

Debian is now Secure Boot™ Compliant, whatever that implies, for good or evil.

AppArmor is enabled by default... oh wait, it's already enabled on my systems. I don't even what the hell is this, but as long as it does not get in my way, I'll let it slide. GNOME uses Wayland by default, too bad noone sane uses GNOME AKA "please don't theme our Apps™".

Also, this:
2.2.12. Merged /usr on fresh installs

On fresh installs, the content of /bin, /sbin and /lib will be installed into their /usr counterpart by default. /bin, /sbin and /lib will be soft-links pointing at their directory counterpart under /usr/. In graphical form:

/bin → /usr/bin
/sbin → /usr/sbin
/lib → /usr/lib


When upgrading to buster, systems are left as they are, although the usrmerge package exists to do the conversion if desired.

This change shouldn't impact normal users that only run packages provided by Debian, but it may be something that people that use or build third party software want to be aware of. The freedesktop.org project hosts a Wiki with most of the rationale.

I can hear the furious laments of pain of Troo UNIX® Way sysadmins as they lose another of their cherished '70s traditions. The rest of the world just says "meh".

Default GCC version is 7.4 and 8.3. Yes, for the first time (ever? in a long time?) you have a choice! Not that you can use the latest GCC 9.x/10, but hey, we're now up to 2017s-era choices! Default PostgreSQL is 11, maybe it's time for me to move on... if only someone ever revived the pgAdmin III branch with support for newer PostgreSQL versions (if you didn't know, pgAdmin 4 got infected by the phoneworms and became a shittyass Chrome-in-a-can® webapp that is so unreliable it actually borders in uselessness)

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Dinosaur

Post: #425 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Will I still able to browse websites, watch porn, play my Steam videogames, and rant about shit that bugs me once X is dead?

If yes, then go ahead, Wayland in the future all the way, as I don't care for as long as you don't let the UXtards to get in the middle.
But I can hear the extremist UNIXoid fanatic nerds screaming in horror as yet ANOTHER of their beloved legacy traditions get into the chopping block. Also, letting the GNOME guys in charge of ANYTHING involving public-facing software is NEVER good, no matter if the reasoning is solid (they will find a way to ruin it anyway).

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Dinosaur

Post: #426 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Or we should abandon computers for good.

I want an OS that stashes all binaries in /DANGERMINES, but I guess that I can't have that, hence computers are doomed.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Dinosaur

Post: #427 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by Kawa
Posted by CaptainJistuce
When is the last time an installer actually told you what it was doing in any detail?
I can't be specific enough to name names but roughly half-ish of all applications that used NSIS installers were more than willing to go into detail.

Then there are the old Wise installlers whose uninstaller logs were in plain, human-readable text, a play-by-play action of each action performed. You could even pick which actions to undo when uninstalling something: handy when getting rid of some shareware but without tampering with some OCX which by chance might be used by something else you could actually care (and for which whoever wrote the installer script forgot to flag it as a shared file): you could deselect unregistration/delete for said .OCX and get rid of everything else.

I've yet to see another uninstaller with such a fine-grained control.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-08, 21:11 in Games You Played Today REVENGEANCE (revision 1)
Dinosaur

Post: #428 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
I've been into Super Mario 64 ROM hacks lately.

Unfortunately, it seems the scene there has a severe case of the ZSNES, as most of the hacks I've downloaded only seem to be compatible with Project64. That's a problem for those of us Not Running Windows™ (no sureanem, I Am Not Going To Emulate An Emulator!), because in the case of Linux, we don't have many options for playing N64 games (but the one we have -Mupen64Plus- is actually among the best ones in the HLE arena).

As a rule of thumb, if the hack comes as a .ppf patch, it won't run on M64P (no, I'm not mispatching my ROMs: I've tried PPF-O-Matic 3 under Wine, and the native applyppf by Paradox: both generate valid ROMs but M64P won't even bother booting them). Only The Missing Stars patches and runs under M64P. I've had better luck with hacks shipped as .bps/xdelta patches (it seems people at SMW Central embraced the byuu format for patches, and I've had a good chance to test my Java-based BPS patcher I wrote 6 years ago -yes it works!-). Oh, and a fair warning: none of those hacks seem to run on recent M64P builds! Either the emulator hangs badly (sometimes requiring a reboot for no good reason!) or the ROM hangs after the splashscreen. The ancient M64P build shipped on Debian Stretch actually works fine for playing ROM hacks, so go figure.

Anyway, it seems most hacks are on the "how we can make SM64 more ANNOYING" and "yay more floating islands" leagues. Did I've mentioned how much I hate floating islands? (the last two worlds in vanilla SM64 were nothing short of hell for me - I'll take underwater/lava/quicksands levels any day of the week, thanks). So far I'm kinda enjoying The Missing Stars and Star Revenge 0.5 - Unused Levels. And a meme hack labeled as Super Jeezus 64 (which is nothing but vanilla SM64 with a very very crude paint job on top, to say the least. And the most fitting BGM for Bowser worlds, seriously!)

Posted by BearOso
Videos can be a pain. You could try "winetricks amstream quartz devenum" then add an entry to disable winegstreamer in the libraries section of winecfg. If it's a WMV codec, it's probably not going to work no matter what.

I have Fatal Zero Action, a doujin game installed on my Wine prefix since... what, 2013?
The opening video is a .WMV file. All it needed to get that working was native devenum+quartz, plus installing the Windows Media 9 Format Redistributable (wmfdist.exe).

Other games using more mainstream codecs (like Melty Blood's opening MPEG) have been far more trickier for me, and I'm unsure if I ever got those working.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-09, 01:23 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs) (revision 1)
Dinosaur

Post: #429 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
So, today I wanted to plug my fancy ol' 4:3 IBM T120 display to my (kinda broken) Asus laptop.

Normally you plug the display, whatever video driver is running your PC reads the display EDID, then parses it and tells that this display can go up to 1600x1200@60Hz. Normally. But since all I have is broken computers, the VGA port on my Asus does seem to have nerfed DDC lines (maybe collateral damage from The Great Hardware Loss which killed the HDMI port on this thing). That means that I'm limited to sucktastic 1024x768 blurriness.

Under Windows (and depending on your GPU drivers), you may be able to either specify a custom EDID dump, play custom video modes fuckery, or -if you're lucky- your display OEM may have supplied you with a device driver that tells Windows to ignore whatever EDID has to say and that this baby can actually go up to 1600x1200 any day of the week, not only on sunny Thursdays.

Under Linux, these are your options:

- If you have a nVidia card using the blob, this is surprisingly easy: you're already using something that resembles a xorg.conf (to force Xorg to use the blob instead of silly Nouveau). Just add the relevant CustomEDID line for your desired head, restart X, done (I've had to do it at $FORMER_WORKPLACE, as finding a non-broken VGA cable with the DDC pins wired inside was next to impossible)

- If you're using KMS (that is, i915 or radeon... or if you're unlucky, nouveau), now things become more complex. You're not supposed to rely on Xorg for faking/reading EDID from a file, instead you must go through the kernel. There is a boot/module parameter (drm_kms_helper.edid_firmware, which in newer kernels has been shortened to just drm.edid_firmware... despite EDID not being firmware AT ALL!). Put your EDID files somewhere at /lib/firmware, update your GRUB settings, reboot and... what the fuck do you mean you can't read that tiny 128 byte blob?! Ah, right, we're doing early KMS, which means we have yet to mount our root filesystem and instead we're living at the initial RAMdisk! You have to figure out how to include your EDID blobs on your initrd. Long short story: welcome to the joy of whipping up your own hook scripts, like an ANIMAL:
#!/bin/sh
# /etc/initramfs-tools/hooks/include-edid-data

PREREQ="udev"
prereqs()
{
echo "$PREREQ"
}

case $1 in
prereqs)
prereqs
exit 0
;;
esac

. /usr/share/initramfs-tools/hook-functions
# Begin real processing below this line

EDID_PATH="/lib/firmware/edid"

for edid in ${EDID_PATH}/* ; do
copy_file firmware "$edid" "$edid"
done

exit 0

(had to modify a somewhat popular script out there since 1- it was ugly, 2- it implied you're using a single EDID which may or may not be your case, and 3- it didn't really worked)
Then rebuild your initrd (update-initramfs -k <your kernel> -u), and reboot.
...except that for whatever stupid reason, Xorg still refuses to go over 1024x768, yet it can now tell I have a <garbled name> 20" display! FUCK. And it seems that none of this will work if you hotplug your display (which is expected from a freakin' laptop VGA port!!!)

- Force it with xrandr: add the missing video mode:
xrandr --newmode "1600x1200_60.00"  161.00  1600 1712 1880 2160  1200 1203 1207 1245 -hsync +vsync
xrandr --addmode VGA-1 1600x1200_60.00

You're going to have to do it anyway, no matter the case as the kernel knows better than you.

But you can avoid all this unnecessary headache by using non-broken computers and cables where all of the expected signal pins are actually wired inside. Don't be me, guys :/

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-09, 13:03 in Games You Played Today REVENGEANCE
Dinosaur

Post: #430 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
At least it's nice to see that now there are affordable N64 flashcarts so you can actually test on hardware, so you can resist the temptation to make games for the ZSNES Project64 gaming console.

Not that it helps Mupen64Plus users that much (I do know at least of a demo that won't run on anything that isn't an actual console), but then emulators and romhackers have the same ultimate goal: to accurately target the original hardware. In the meanwhile, I guess I'll have to keep two separate M64P installs: one for hacks and another for games. Kinda annoying, but not the end of the world.

And yeah, it was amusing to see back in time how the GBA was emulated even before going retail. How is that even possible?! (IIRC only the NDS has official emulators on the devkits)

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-09, 19:48 in Games You Played Today REVENGEANCE (revision 1)
Dinosaur

Post: #431 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
I've just tried CEN64 on this ancient laptop.

I'm pleasantly surprised: it runs at (roughly) half speed! (with or without multithread doesn't seem to make a noticeable difference) And that's on a lowly Sandy Bridge laptop i5 from 2012! You can actually play SOME games with this (I'm finally glad to find an emulator that can run the N64 Puyos with perfect graphics; on M64P the best I can do is GLideN64 with either perfect gameplay graphics but glitched title/menu screens, or crystal-clear menu/title screens but wrong GFX during gameplay on Puyo~n)

You guys with access to fancier computers should have a much better experience with it, maybe even fullspeed. If a dynarec is on their plans, can't wait for it then.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-09, 20:29 in I have yet to have never seen it all. (revision 3)
Dinosaur

Post: #432 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Some retro computer enthusiast tried "mining" buttcoins on a 1960s computer:
https://hardware.slashdot.org/story/19/07/09/0545255/bitcoin-mining-on-an-apollo-guidance-computer-103-seconds-per-hash
The computer system: https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

The results? A total and complete waste of money and electricity, all in the name of lulz (and the guy needed a reasonabl workload for stress-testing his repair job, or something). But hey, this thing went to SPACE, where no buttcoin has been before.

Now, how about porting higan to this thing...

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-12, 04:41 in I still HATE smartdevices (revision 2)
Dinosaur

Post: #433 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
BLU phones really make me turn blue.

Today's victim: a BLU Advance 4.0 (A270a) with the same boot logo hang as every other lovely broken Android turd that lands into my hands. Mediatek-based phones are double-edged swords: they break so easily, yet they're fairly easy to revive (plus, I'm lovin' the native Linux flasher). A few notes (because why not?)

- Getting the phone to flash took several attempts for whatever reason. Kill ModemManager, just in case.

- The phone had A07 firmware. I was only able to find the latest one, A10 (which comes with newer BLU branding over the same ancient Jellybean build that your favorite crapps already have deprecated). This caused the Mediatek flasher to scream at me that something has changed in the ROM structure, therefore I have to format the phone first. If this is absolutely required for the firmware download to actually work, WHY YOU DON'T DO IT ON YOUR OWN?! Gee, a "Full format is required, Do It / Cancel" dialog would have been handy, instead of the useless "THOU SHALL FORMAT! OK / More Info" currently in place! *sigh~*. Format tab-> Auto format-> Start -> you're ready to download firmware.

- After phone boots for the first time, insert SIM cards back. Oh wait, you have no service now! Even worse, your IMEIs are gone! BOTH OF THEM. Apparently this is expected even if you do a factory reset or switch ROMs because lolMediatek (seriously, why IMEIs don't live in OTP EPROMs anymore?!). Luckily for us, these aren't Qualcomm phones (where you can get into a world of pain if you end with no IMEI and no EFS backup, and this is the reason of why I'm not rooting my ZTE yet) - you can actually "repair" your IMEI yourself using nothing but the phone itself, and depending on your phone, you may not even need to root the bastard. Unfortunately in my case, I DID have to root (the dialer app filters out the Engineering Mode code on this one), but you can unroot after fixing stuff.

- There is no TWRP for this thing (only hacked CWM builds that are impossible to download nowadays), and I doubt Magisk supports devices that old, so your rooting options are quite limited. I used good ol' Kingo Bloat Root, worked at the first try. Knowing how invasive is Kingo, and how unstable is SuperSU, I'll keep my rooting duties to the bare minimum on this one (repair IMEIs, do minimal debloating as this thing thankfully is almost vanilla Android with few Google addons) before turning back this thing to its owner. Unrooting is a two-tap operation, and doesn't seem to leave traces.

- GPS seems to be broken (it actually was broken before the reflash, according to Factory Mode testing). Not that its owner cares (it's an old lady that only uses the phone for texts, calls, and WhatsCrapp), so I'm not going to bother researching possible fixes.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-12, 12:05 in I still HATE smartdevices
Dinosaur

Post: #434 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Make your guess.

And yes, what I actually had to do was technically illegal in most of the world, but it was required to make the phone work again as a phone, and not as a palm-sized tablet computer. Once again: why those things don't live at an OTP memory?! (In the ancient times that used to be the way)

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-12, 19:04 in I still HATE smartdevices (revision 1)
Dinosaur

Post: #435 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
The IMEI (and its equivalents on other networks, ESN for CDMA IS-95/TDMA IS-136, MEID for late CDMA2000 IS-2000 devices) is supposed to be burned on baseband's OTP ROM, both technicallyt and legally.

In a era previous to the smartdevice, changing IMEI/ESN was extremely illegal, and you needed a very expensive service box for that (the feature was included under the dubious "repair IMEI/ESN" feature banner, which was a misnomer as there was nothing to repair; a broken OTP most likely means the phone would not boot or something else). Since you can't alter OTP ROMs, said boxes resorted to apply firmware patches to the phone flash memory, forcing it to read the serial number from flash instead of OTP. Said patches were highly version and carrier specific, which means that if you ever had to update/reflash your firmware, the phone would revert to using the serial on the OTP.

Suddenly, device OEMs may have decided that they could save half a cent by forgoing the need to separately program an OTP, or some similar BS (I am not into the phone industry biz, so I might be talking out of my ass, but whatever), so they decided to move some of those previously read-only sensitive byte sequences to plain flash (often protected behind secure storage partitions, TrustZone or other enclaves, or whatever). And since you can't expect quality from fly-by-night Chinesium phone factories, chipset OEMs stopped caring, or whatever. Or maybe protecting Hollywood from people ripping Netflix on their phones is much more important than actually preventing phone fraud/theft.

This has nothing to do with IMEI-spoofing apps for smartdevices, which is another completely different thing (they're spoofing apps, not the baseband). Also, a phone with a broken/erased IMEI does get blocked out of mobile networks for the same reason sysadmins and network gear may block people trying to connect with zero'd MAC addresses: address collisions!* A phone with an erased IMEI may report with a random IMEI (there is a check digit, but it's only meant for labeling, and it's not part of the actual number sent to the base station) which may get accepted, or will report with an IMEI of all zeroes... which will collide with the other 360 handsets whose firmware have commited sudoku that day. Or maybe default to a hardcoded (and hence easy to blacklist) ESN that is shared with all of the devices of the same product line/model.

I'm not sure to which IMEI those BLU phones do default when the IMEI is erased, but all I can tell is that while the radio will scan and detect mobile networks just fine, the carriers will refuse to let the device register into the network without a valid IMEI. Once I "repaired" the IMEIs on this thing, Movistar gladly let the phone join the network. In the case of Qualcomm phones (like my Z835), a damaged/erased EFS means a all-zeroes IMEI, which cannot exist and therefore leads to a brick (even if the GSM/UMTS/LTE radio can actually power up and blast a signal over the airwaves!)

*A similar problem appeared during CDMA's transition from ESN to MEIDs, as not all networks were compatible with the new serial format, which would seriously hamper roaming capabilities. An interim solution was devised: the pseudo ESN (pESN). The pESN is actually the last 24 bits of the MEID SHA1 (IIRC), prefixed with "80" (which was previously a reserved range). Since only a part of the SHA1 was used, collisions were a real concern, but the industry downplayed the risk, as eventually all CDMA networks would have migrated to MEID (or shut down, which was what actually happened to most CDMA networks around the world). I never heard about people having problems while roaming with their MEID phones on older ESN-only networks...

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Dinosaur

Post: #436 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Operation "To Buster or bust!" starts!

The craptacular CANTV DSL decided to give me a truce last night, so I took advantage of that to start moving my gear to the latest stale shiny. The first target is the machine I use the least nowadays, my IBM TV box (remember: 686-pae, 32-bit can't die even if they're killed with fire).

After downloading ~1.2GiB of packages, the update took like 2 hours or so (complete with a HDD error after the first reboot, yet a subsequent 2-hour SMART selftest gave the typical politician speech "everything is FINE!". Ah well, I still had plans to clone this thing anyway...), everything actually worked fine (even Plymouth properly applied the newer bootsplash before the first reboot, still on the backported Stretch kernels!).

I didn't had to redo my LIRC settings despite the jump on minor version number (unlike my Jessie->Stretch upgrade). Modify lightdm configuration to reenable autologon (this is a TV, you're not supposed to logon with a password on those!), check that the TV tuner still works (it still does, and the tuner can is still busted, thanks to Interdeepfryers®)

And then... ALSA broke because Pulseaudio happened.

Before you guys get your Poetteringware hateboners at full blast, let me tell my setup at home. Yes, I don't mind Pulseaudio... on my laptops, with their dinkyass AC'97/HDA codecs. But then, this specific setup HAZ a Real Sound Card™, a good ol' SB Live! (EMU10K1), which while still bundling one of said dinkyass AC'97 codecs somewhere in the DAC/ADC path, it is neatly concealed behind a honest-to-God DSP, complete with a hardware mixer (remember when computers used to have serious muscle on their sound subsystems?). Why in the hell would I need the services of Pulse when I have a perfectly good piece of hardware that lets me have 32 threads in simultaneous ghettoblaster concert at the same time without the need of extra software?!

In the past, disabling Pulseaudio on Debian was trivial (and with that approach, you could even re-enable it back should you ever need to use its services for whatever reason). But that setup no longer works with Buster. Ha, audio is now busted! Even worse, since developers and distro maintainers know better than you, there is no way to kill the PA daemon while ensuring it stays dead (another thing that doesn't die when killed - maybe we need a F/SN-based Linux distro?). No, "autospawn = no" does nothing on client.conf, and I can't be assed to research why. I just wanted my goddamned EMU10K1 back!

Anyway, turns out that you need to undo the instructions on that Debian wiki, and purge the pulseaudio package (which contains the daemon/client):
dpkg-divert --rename --remove /usr/share/alsa/alsa.conf.d/pulse.conf
dpkg-divert --rename --remove /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf.example
dpkg-divert --rename --remove /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
apt-get purge pulseaudio

# If needed, also delete /etc/alsa/conf.d/99-pulseaudio-default.conf.example, if it still exists

Reboot, and let your voice be heard~
(you WILL need to redo your mixer settings, hope you have a screenshot or something! Don't be like me...)

One system done (but that was EASY MODO), two to go...

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-13, 01:32 in I still HATE smartdevices
Dinosaur

Post: #437 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by sureanem

you can actually "repair" your IMEI yourself using nothing but the phone itself

Do you need to reboot it for this? Seems like you could vastly improve privacy by randomizing IMEI per SIM card/session combination. Curious that none of the 'privacy phones' did this.

A reboot is actually required, indeed.

Also, none of the "privacy phones" implement this because that's, well, illegal.

Oh, and having a phone which allows its IMEI/ESN/MEID/whatever to be changed at will means that if yours ever get stolen, you have a fat chance in hell to recover it, because no telco can't track it anymore. It's like selling cars with forged serial numbers, which is a couple orders of magnitude worse than stealing $200 plastic slabs.

Posted by sureanem
But why'd it be illegal to change it though? I can only find information on cloning, which seems more like outright fraud than illegal modification. Surely, using an IMEI nobody else is using should be A-OK?

That's the most typical rationale, yeah - that dates back to the era of analog cellphones, where the security ranged between "none" and "a joke". Technology has marched on, but the laws are still stuck in the stone age. Fraud is still illegal, no matter how you commit to it. That's the typical case of "we can't have nice things because there are assholes in the world".

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-13, 01:43 in Cartoons, imported
Dinosaur

Post: #438 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
What's different between this and doujinshis?

Sure, doujins are kinda at the margin of the law, but then corporations usually don't give a damn, and messing with fanworks is an easy way to attract bad rep, so they let it slide. Yes, even the gross tentacle porn ones.

Still, it's nice to see copyright holders actually extending an olive branch to the fandom once in a while.

...and then, you have ZUN and Touhou Project, where the rules are simple: "I do not want to read your porn AT ALL", "no professional animation works", "do not spoil endings", and "do not sell to baka gaijins until I get first dibs on your preferred sales channel!".

At the other end of the scale, you have happy lawsuit trigger Nintendo, which used to harass doujin circles in the past (not sure if they still do it nowadays).

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-13, 17:15 in I still HATE smartdevices
Dinosaur

Post: #439 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by sureanem
Posted by tomman
Also, none of the "privacy phones" implement this because that's, well, illegal.

How come none of them let you swap out the baseband then? Those are generally quite cheap (<$1), so if you'd build it so that the baseband and SIM pop out at once and ship it with a pack of ten you could probably solve that whole issue.
Then again, you could solve the whole triangulation problem by making your own baseband, and nobody does this either.
I reckon the answer is simple, as always: the people running it are just out to get a quick buck and don't actually care too much about privacy, and the only people who actually care would just buy burner phones.

Now you're getting concepts mixed. If you make the baseband (cell modem) switchable, now by law the ESN belongs to the modem module, which is an extension of the computer device, and therefore it quickly sends you to certification hell. This is one of the many reasons of why noone makes modular cellphones (the nearest example I can think was Willcomm's PHS "SIMs", which were actually a removable cell modem in disguise, and even then that proved to be a dead end)

Stop overthinking this, really. It's far cheaper to just go out and buy another phone.

Posted by sureanem
Oh, and having a phone which allows its IMEI/ESN/MEID/whatever to be changed at will means that if yours ever get stolen, you have a fat chance in hell to recover it, because no telco can't track it anymore. It's like selling cars with forged serial numbers, which is a couple orders of magnitude worse than stealing $200 plastic slabs.

Has that ever helped, though? Short of iCloud lock, which is now broken, I'm skeptical. I mean, you can just swap out the logic board.
It would have helped with ordinary phones, but now?

Ah, logic board swaps. I can't even tell if that's a gray area, akin to "chop'n'weld" (can't remember the exact term right now) rebuilt cars - it's not as cheap as just using a hardware dongle or some app to "repair" an IMEI, but sure as hell is an express way to "purify" stolen property. But then, that's another double-edged sword as I myself have performed board swaps quite a few times on devices with the express authorization of their legit owners. I'm not even sure if I want to get DA RULES involved in this... If we try to regulate phone repairs, we will quickly end into DRM, "repairing is dangerous, therefore WARRANTY VOID IF OPEN", and hot politics water.

Posted by sureanem
Fuck cell carriers, worst industry in existence. Should all be nationalized. [...snip...]
But that's for Politics! Something about cheese!.

As a subscriber of a state-owned telco (CANTV/Movilnet), all I can say to that is: careful with your words, buddy. As evil as can telcos be, you definitely DO NOT WANT to apply the "n-word" to them. But yeah, that's out of scope for this thread.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 19-07-14, 16:19 in Leaked Super Mario 64 Decompiled Source (revision 2)
Dinosaur

Post: #440 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
1) Assuming this ever gets finished, how feasible would be something like, say, a native PC port?

2) Didn't Nintendo used GCC back then? I guess MIPS64 might have been a very new target, so optimizations were not exactly there yet - "it builds, ship it!" is not really new. They used SGI's toolchain (IDO), but I'm not sure of which compiler it had - some flavor of GCC is not unlikely.

Oh, scene drama! Also, Nintendo DMCA'ing some asses is in the order for today.

Hackernews coverage: https://news.ycombinator.com/item?id=20418577

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
    Main » tomman » List of posts
    This does not actually go there and I regret nothing.