Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror

Comment Re:UAC - A Double Edged Sword (Score 2) 187

by kilogram (#49456491) Attached to: LG Split Screen Software Compromises System Security

I wouldn't be surprised if LG ran into a COM issue with Windows and decided to make the program for reliable for the user by disabling UAC instead of resolving the problem in a different way.

There really isn't any reason they needed to do this, besides incompetence or malice. I know, I develop commercial software that does much the same thing as their software.

I commented further down with more details regarding why.

Comment They didn't have to (Score 3, Interesting) 187

by kilogram (#49456353) Attached to: LG Split Screen Software Compromises System Security

There are ways to work around UAC without disabling it in this case. I know, because I wrote MaxTo, which does much the same things, and works with software running under UAC.

If you want MaxTo to work with UAC, you'll need to run MaxTo elevated. If you say deny elevation, it simply won't work with elevated software.

I'm pretty sure LG just took the "easy way" out (or they may have nefarious purposes, but I won't speculate), instead of figuring out how to communicate between elevated and non-elevated processes.

To do this sort of thing, you'll need to divide your software into a few parts. First and foremost, you'll need to install a global system hook. That hook has to be written in unmanaged code (meaning C/C++). You'll need software that controls the hook (but it can be written in a managed language). Now, both the controlling software and the hook has to be compiled as both x64 and x86 code. They will probably also have to communicate with eachother across the x86/x64 platform boundary.

Now, to get the software to communicate (using window messages) across the UAC boundary, you have to specifically let Windows know which window messages your app will accept from the other side. This is probably the step they missed. You do this by using ChangeWindowMessageFilter or ChangeWindowMessageFilterEx .
Space

Comet ISON Survives Perihelion (Barely) 62

Posted by Soulskill from the still-alive dept.
An anonymous reader sends this update from NightSkyInfo: "Yesterday, when Comet ISON plunged through the solar atmosphere and behind SOHO's coronagraph (the black disk designed to block out the direct light from the Sun), its nucleus dwindled away to nothing and most of the tail simply evaporated. Everyone assumed that the comet completely disintegrated and died a fiery death. However, several hours after perihelion, ISON began to brighten up again. It is now distinctly evident on live images from SOHO, looks like a comet, and continues to brighten as it moves farther away from the Sun." Experts are unwilling to say precisely how intact the comet is — we'll need more data to make a conclusion about that — but astrophysicist Karl Battams says this is their best guess: 'As comet ISON plunged towards to the Sun, it began to fall apart, losing not giant fragments but at least a lot of reasonably sized chunks. There's evidence of very large dust in the form of that long thin tail we saw in the LASCO C2 images. Then, as ISON plunged through the corona, it continued to fall apart and vaporize, and lost its coma and tail completely just like Lovejoy did in 2011. (We have our theories as to why it didn't show up in the SDO images but that's not our story to tell - the SDO team will do that.) Then, what emerged from the Sun was a small but perhaps somewhat coherent nucleus, that has resumed emitting dust and gas for at least the time being. In essence, the tail is growing back, as Lovejoy's did.' Here's a GIF of the comet rounding the Sun (put together by Emily Lakdawalla).

Slashdot Top Deals

Quark! Quark! Beware the quantum duck!

Close