![[oki]](/images/smilies/net_thumbsup.gif "Ok!")
Sangreyfuego escribió:Riwer escribió:CrusardGameamos escribió:
El rediseño de la interfaz estaba prevista desde hace mucho tiempo, tienes el rediseño del chat desde antes del anuncio de la Epic Store. Asi que este rediseño no es culpa de la competencia, sino que ya estaba planeado.
Y si, la competencia es buena, pero hay competencias y competencias, y como lo hace EPIC me parece muy rastrero.
Haz una competencia leal poniendo buenos precios, regalando juegos, incentivando la compra de juegos en su plataforma de alguna forma original, añadiendo caracteristicas interesantes... Pero no con exclusividades.
Competencia es vender el mismo producto con mejores precios o servicios, no quitar productos a la competencia a base de golpe de talonario.
Edito: Te sorprenderia saber la cantidad de aplicaciones que utilizas en escritorio como en movil, que son simples navegadores con funciones extendidas. (Epic es una, discord es otra)
Me niego a pensar que me estes diciendo eso en serio, porque si me quieres vender, o ya remotamente te pienses de verdad, que tras 10 años de interfaz de mierda es justamente ahora cuando sale por "seguir un roadmap que nunca existió", ni me molesto en responder.
Menuda pata colega, hay cambios bastante importantes de interfaz todos los años desde que existe steam.
Por otro lado, steam se puede personalizar al 100%, hay que informarse mejor.alvaro200 escribió:Forheit Law escribió:Aunque es un poco offtopic, veo que nadie comenta las noticias acerca del spyware que es el launcher de Epic Games. Hay un hilo de Reddit explicando de manera muy minuciosa acerca de este asunto. Que la competencia es importante, es una obviedad, pero hay competencia y "competencia". Tan mal no lo hará Steam si Epic copia determinados contenidos del sistema de Steam
El problema con el supuesto spyware de Epic, es que no es algo seguro ni esta nada claro. En esos mismos hilos de reddits hay varios ingenieros informaticos explicando que hace cada cosa y por que, y que en definitiva pueden ser usos normales y corrientes de cualquier app.
De eso nada, desde el minuto 1 salio epic explicandolo y dando excusas penosas que como mucho sirven a los que quieren creer que no pasa nada.
Estas excusas son mas o menos que quieren saber que juegos tienes y te interesan para ofrecerte una mejor experiencia en su tienda. Lo de los amigos y sus juegos ya tal...
Nada mas instalar el programa, sin ni siquiera abrirlo, el launcher ya extrae informacion de steam.
"As for poking around for DLLs, especially fiddler, it might be anti-reverse engineering and anti-cheating stuff. It's shady, but anti-cheat shit is going to look shady as fuck and poke around in memory and enumerate your processes and potentially DLLs like that. Cheat prevention requires some serious shit, sometimes getting into ring-0 and running along OS code like a driver.
It looks like it checked for Fiddler and I figure it might be checking to see if you're capturing the internet traffic and doing anything funny. It obviously doesn't want you reading and modifying the traffic it sends. That is probably anti-hack sort of stuff, but it could also be they don't want people to analyze what it sends at all. It's concerning and also not concerning IMO. It could mean they send back a shit ton of metrics they shouldn't need to record, it could be they're just preventing game hacks and preventing people from reverse engineering how it does that, and how it notifies Epic stuff.
For example, let's say you run WallHack.exe, some common hack for a game. They enumerate the processes and phone home, discover you're a hacker, then ban you... but someone uses fiddler and sees them doing that, and removes WallHack.exe from what it phones home, now they don't know. Well, they're going to want to know to trust what you just sent, so they might also check for fiddler and burp proxy and stuff, and then just not let your game launch if you're fucking around or something.
Anti-cheating/hacking is a crazy, crazy world where it's technologies and counter-technologies and going lower and lower level until someone wins. They do everything they can. I've heard that sometimes hackers even go pretty much ring -1 by hooking into a hypervisor running a VM running the game... People go to great lengths to hack, and they go to great lengths to prevent hacking.
If they try to do anti-cheat stuff, there's going to be a lot of false positives that look really bad but might be legitimate anti-cheat techniques. But, they could also be recording tons of metrics and selling data. There's nothing stopping them. I don't know. The kind of info they would need to REALLY attack cheating would also look suspicious af, so it's hard to know without being on the inside. I'm honestly not surprised, and it's not too much of a deal breaker for me... the PC I use to game, I don't use for anything else that's personal. You kind of just have to accept that anti-cheat stuff is going to do shady stuff because it has to."
"The JS file looks like a user interaction logger for a webpage, and its a common practice to track every last fart of a user on serious projects (including actual browser contents capture). I did not dig deep tho, as it's evening already and minimized code is a bitch to read. I'll just go on a limb here and assume that epic client is just an instance of a browser wrapped in some launcher/api provider (Steam seems to work this way BTW). Which may explain its attempts to access IE cookies, but still shady as fuck.
Edit: even spying issues aside, my problem is with their non-competitive business practices: getting a market share by buying game rights as "exclusives" and not creating a competitive product."
EGS isn't trying to access DLLs in Fiddler directly. Fiddler adds its installation folder to your %PATH% variable on-installation (so you could run it by just typing "fiddler"). When you load a DLL by-name and not by-path (which seems to be the case since it looks like an import table entry, which are only by-name), Windows goes through all the folders in your %PATH% looking for the file you named. Fiddler was one of those folders.
As someone else said, "tracking.js" looks like some analytics library like almost everyone uses. The embedded store itself is probably a web frame that uses analytics because their web development department (like all of them) wanted to.
Reading about your root certs, IE COM classes, IE cookie folders, and other IE-related things are all part of WinHTTP. (and ironically why you can even MITM it with Fiddler, since if it used some standalone HTTP library like libcurl it wouldn't accept your new root CA) That happens automatically when you create a session or connection and isn't Epic's doing, nor is it malicious.
The hardware survey bit is a little privacy-invasive but it's probably the same hardware spec gathering that AAA game devs already do without asking you (it's in the EULA), Steam is more of an outlier here.
EGS talking to itself is just standard IPC practice: some apps use localhost sockets (a common Linux practice), some apps uses pipes, etc.
EDIT: Thanks for the gold random stranger!
I sorta have a headache at the moment (nothing caused by this post of yours) so I won't go through all of the post, but the start of it here is something you should really throw out as its irrelevant.
Epic as with most other applications use built-in technologies and APIs in the OS to set up connections. That means it goes through the integrated Edge/Internet Explorer components of Windows and subsequent dependencies (certificate store for validating SSL certificates, Internet Explorer/Internet Options registry keys to fetch active configurations etc) when it establishes online connections.
This is what you see here in Process Monitor... Epic's process going through the OS layer to establish TCP connections according to regular HTTP(S) traffic.
If you would've checked what process listens to port 8888, you'd find Fiddler at the other end.
That "severe mental disorder" is the EGS client talking to Fiddler, since you're using Fiddler as a local HTTP(S) proxy on the same machine.
I can't be bothered going through the rest of the post, but the start of it definitely showed that you're an amateur and doesn't realize that there's no real separation between OS components and third-party processes when viewed from the perspective of Process Monitor. You're viewing everything the process does while running, including stuff that's invoked as part of an underlying component.
For example, the simple use of WebRequest.Create to fetch a single webpage online will also cause underlying IE/Edge components of Windows to validate SSL certificates (i.e. go through the Certificate Store of Windows) and check relevant Internet Options configurations (registry keys etc "related" to IE/Edge).
![[360º]](/images/smilies/nuevos/vueltas.gif "como la niña del exorcista")
