It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
My biggest concern is the security risks inherent in a low grade developer who is ill prepared to handle the data they are retrieving (legally or illegally doesn't even matter at this point to me) taking my data with a substandard encryption and endangering me. "It only attacks the pirates" you say?

How about the fact that it is always present and the security risks go even higher if someone else can trigger and intercept the traffic. Those are my primary concerns. Not with this software, as I don't have any interest in FSX or its mods, but rather in other software whose developers may see this incredibly boneheaded idea and think "stealing customer information? BRILLIANT! Why didn't we think of this sooner!"
low rated
avatar
RWarehall: And the example you give doesn't apply here. That worm self-replicated and did damage to the systems and as such violated the appropriate laws. Back to what I said about intent to defraud or do damage. Because I actually took the time to at least read the various laws. Plenty of software accesses information on one's computer. But the laws have criteria which differentiate between what is legal and what is illegal behavior. Plenty of people call Steam's overlay "malware" or the same with ad delivery software, yet they are not illegal. And that is because neither is attempting to defraud or damage the computer.
avatar
joppo: Nope, plenty of people call Steam's overlay malware because they don't actually have a clue about neither the legal nor the technological aspects of Steam, and those tech aspects are the first reason why it doesn't qualify as malware. If you're going to quote people's opinion, either use your own (with caveats) or quote specialists on the subject matter. Bringing up random clueless people and then reducing all their arguments to "wrong" because you can prove they are wrong about something else is a hell of a fallacy.

Also as you said my example "doesn't apply here. That worm self-replicated and did damage to the systems..." Hold on. Aren't you the one that kept throwing around "show me that that is the legal definition of malware"? Well okay then, where does the law say that it has to propagate in a specific way to qualify as malware? And don't bother arguing that it just doesn't qualify because it didn't do any damage, because as you can see below...

avatar
RWarehall: This part of the article you link seems to show it probably is not illegal in the UK either...
[snip]
avatar
joppo: You read all of that and you happened to leave out the very adequate next paragraph. Allow me to reintroduce it:

"The deliberate introduction of any malware will meet any of these requirements by taking memory and processing from the system and feasibly damaging the system."

Do you deny that the uninvited malware takes up memory and processor time it was never intended to by the user?
Read the article again why don't you. It's specifically talking about "malware (such as a virus)." All infections are going to be using memory and processing time as they continue to run in excess of existing programs.

The problem here is that this IS the program as defined by the developer. You would have a really hard time convincing any judge that this is not DRM but malware instead given that it is part of the installer, runs once and stops just like the rest of the installer and is being used to enforce digital rights.

You keep looking at this with blinders starting from the concept that this is "obviously" malware to you. It will not be so "obvious" to a judge who will carefully weigh arguments by both sides.

But let's also be clear, if you over define a term to the point a phrase becomes completely meaningless in a law, your argument will fail. All programs use memory and processing, so there has to be a clear distinction why this program damages a computer. By your argument, ALL programs apparently damage a computer by using memory and resources. A judge isn't going to buy that argument because it makes the term "damage" completely irrelevant. Then why is that term included in the law?

It makes sense with worms and viruses which reproduce or continue running as an extra process, continuing to use resources slowing down a system. It doesn't make sense with a piece of code which runs once and stops.

You are clearly trying too hard to make an exception of this.
low rated
avatar
paladin181: My biggest concern is the security risks inherent in a low grade developer who is ill prepared to handle the data they are retrieving (legally or illegally doesn't even matter at this point to me) taking my data with a substandard encryption and endangering me. "It only attacks the pirates" you say?

How about the fact that it is always present and the security risks go even higher if someone else can trigger and intercept the traffic. Those are my primary concerns. Not with this software, as I don't have any interest in FSX or its mods, but rather in other software whose developers may see this incredibly boneheaded idea and think "stealing customer information? BRILLIANT! Why didn't we think of this sooner!"
That is a big concern and probably should be a major concern of every Internet entity. The thing here is that we don't know what level of security they use in house. Everyone seems to make assumptions based on very little.

Remember not long ago when GoG used unsecured pages which carried our login tokens. They claimed our passwords were safe and it was just a token, but even a token out in the wild is unfortunate.

As to worrying about people triggering it, the only way I see that happening is a complete URL hijack because it triggers only during installation. If you are worried about that, then there is far more to be worried about as your credit card information would be intercepted in buying the software as well from a spoof site.

And its not "always present". The risk window is only during the installation.

But frankly, I doubt we have much to worry about from other developers following course. It's not like this dev is going to get anyone arrested. These crackers are very likely out of his reach. Most probably living in a country which doesn't make piracy a high priority. No one else is going to waste their time and effort tracking people down on the net to accomplish nothing. Not to mention, other developers aren't stupid enough to risk losing many legitimate customers with fear about their passwords over pursuing pirates they are unlikely to catch. And its not like catching one pirate is going to stop the piracy of their products anyway. In short, this "wonderful" plan of his was a good way of driving off paying customers in pursuit of pirates he is unlikely to catch. A very bad trade off. No other developers will follow...
Post edited February 27, 2018 by RWarehall
avatar
RWarehall: <snip>
I disagree with... well, it would be easier to say what you and I agree in, but I won't have time to write the reply your opinion deserves for a while. I am at work and it's turning into a busier week than it was when I first engaged you. And I'm having trouble with my internet access at home (thank GOG for their DRM-free games)

Maybe I could write a reply at home and and take it to work to post it once I come online but, eh, too much trouble.
Post edited February 28, 2018 by joppo
The recent flight sim thread reminded me of this thread.

Looks like they got away with what they did.

avatar
RWarehall: Remember not long ago when GoG used unsecured pages which carried our login tokens. They claimed our passwords were safe and it was just a token, but even a token out in the wild is unfortunate.
That was similar to the issue I reported back in December. Logins appeared to be dropping from secure https to unsecure http and then back again. Or at least that's how I read the headers.
Post edited May 09, 2018 by drmike
They're at it again and threatening reedit moderators over the reports:

https://torrentfreak.com/flight-sim-company-threatens-reddit-mods-over-libellous-drm-posts-180604/