slipstream-

You misunderstood: the commenter said they'd provide a passworded wifi network and a sign somewhere saying "visit this URL to get the password for the wifi!"

People would visit that URL using mobile internet...

I also heard "too well", as in, developers just wanted to use their android apps instead of making windows apps.

It wasn't totally canned though, it became the Windows Subsystem for Linux.

>If you can simply provide "up to" on something, then I wanna sell you a box for ten bucks that contains up to a million dollars!

So, scratchcards then?

IMO, the problem with disclosure is one of the biggest problems with infosec right now...

Ah, OK.

Doesn't seem to be working in Edge.

Line 33: Object doesn't support property or method 'forEach'

I'd actually be interested to see the pitches made by these kinds of people...

I've written small command line scripts in PHP before (without any helper libraries). Using PHP for such things is nice when interfacing with web services (JSON parsing, SimpleXML, etc).

Perhaps Peachpie, when it reaches production quality, will also help with that, as then calling .NET (and maybe, through that, WinRT) APIs from PHP code will be made easier.

as InfoSec Taylor Swift once said, "potentially unwanted programs" are just malware with a legal team.

What do you expect, from an entity that advertises via spreading malware/PUPs?

https://blog.malwarebytes.com/detections/pup-optional-bookin...

>Or, wait until Microsoft finalises their x86 translation layer for Windows 10 ARM

ARM64, not ARMv7.

Also, from what I hear, binaries need to be compiled specifically for this - others just use a slower JIT emulator.

I thought at first that this was to do with memory mapping/banking...

I tend to buy from a UK vendor who I found out about through favourable magazine reviews. The last few times I ordered from them, they offered no-OS options (which in practise meant a preinstalled but non-activated Windows, and Windows reinstallation media provided).

>modern malware does not try and break your system.

Unfortunately, malware has shifted back into breaking systems, under the form of ransomware.

The website seems to be a blogspot blog on a custom subdomain...

If you sideload it as an unpacked appx in developer mode rather than an unpacked extension it doesn't do this.

I reversed the shellcode, it's almost exactly the same used in 2013 (freedom hosting): https://twitter.com/TheWack0lian/status/803736507521474560

I agree. Malware has been known to install vulnerable signed drivers to get unsigned kernelmode code execution.

>On the other hand, Microsoft could have easily gotten a much more "robust" lockdown - by simply demanding mandatory, unchangeable Secure Boot like on the ARM tablets. But they didn't do that.

Didn't you hear that Secure Boot is basically broken?

7.1 wasn't just a version number that China DOS Union made up but is the actual version number of win98's (and 95 OSR 2's) DOS.

So, default wallpapers in early Windows 95 builds.

The first Preliminary Development Kit had an "Under Construction" wallpaper. The second one had the same wallpaper but tiled. Beta 1 had a different "Under Construction" wallpaper.

Of course, after PDK1 leaked far and wide, MS implemented some serial protection in PDK2 up to beta 2 (different from the one in the RTM; however the RTM's setup has remnants of it). Given that the leakers were involved with the warez scene, however, the skilled reversers that the builds were passed to easily found the backdoor that had been put in so that those on MS' internal network didn't have to enter the serial, and just patched a few bytes in the setup to abuse that.

The interesting part of this serial was that it was in two parts. One part was the "beta site ID" and half of the "password"; if this was valid, but the second half of the password wasn't, setup would appear to continue... until the point it would copy files, upon which it errored out with a message "General error 57, please contact your beta administrator".

This misdirection was discussed at the time, with some people believing the error at face value. This continued with the foundation of communities to preserve and discuss such builds several years onwards. The last half of the password was the hex form of the first 16 bits of an MD4 hash (this code was written in around autumn 1993!) of the beta site ID, the first half of the password, and... a string inside the setup that was used as the titlebar text for the error message, which would be something like "Microsoft Chicago Preliminary Development Kit 2, November 1993".

This part of the serial algorithm was finally reverse engineered, and a key generator made....in 2014.

Afterwards, some early Internet Explorer 4.0 builds were discovered. They used the exact same serial algorithm as the early Windows 95 builds. And had the exact same "MS internal" backdoor.

(Um, I think I may have just ruined one of Raymond Chen's future blog posts.)

"help track down leaked builds of Windows"

If you're talking about public leaks (rather than just private leaks to a few individuals), surely they're not that hard to find?

I wonder if you mean the leakers?

(for the record, I'm a moderator of a forum which discusses said "leaked builds of Windows"; and I help try to find and preserve those that leaked long enough ago such that they have almost disappeared)

MS' own advisory says you don't need physical access (only admin rights).

Already fixed, 10 minutes after I noticed myself.

Yay for Let's Encrypt.

No, it doesn't. It merely prevents the use of one way to install some policies on Windows RT devices.

On Phone, the exploit chain to do exactly that is already public.

Maybe so; but I didn't want to implement too many effects. :)

There is lots of evidence that a port of NT to ARM64 exists.

I like dnspy, which is a fork of ilspy.

Snowball was WfW 3.11.

WfW 3.1 was Sparta.