I assume this means that you have no fits with duplicate names. Alright.
I just tried 2.10.1 exe build under Wine and it worked for me. Curious about logs of failed attempt (stored in /home/user/.wine/drive_c/users/user/.pyfa for you, most likely). Also you could switch SSO login method from server to manual (as in this case there’s some browser-server interoperability issue, by the looks of it).
By the way, on Linux pyfa is not that hard to set up to run from source. Preferably you should have OS-provided wxpython for python3, the rest can be installed via “pip3 install -r requirements.txt” (wxpython also can be, but as it has to be compiled from source - you need quite many development packages for that).
Wondering if it could be as simple as the firewall getting in the way of the returning data? Unsure exactly how it works on linux, but windows simply allows an app to do whatever it wants, I didn’t think Linux was as permissive.
@elitatwo You may find something in the /var/log/messages (or equivalent spot on mint/ubuntu), this is assuming the fw logs denied packets by default.
The path is /home/YourUserName/.wine/drive_c/users/YourUserName/.pyfa
However, that ESI character thing tries to import my empty fitting browser (I finally managed it with the manual setting) on TQ.
Maybe I wasn’t clear but all of my fittings and corp fittings are on Singularity.
I keep my fitting browser on TQ empty, so I can import my files when a new mirror comes. @CCP_karkur unfortunately I have to delete all the fits that we have in our corporation fits again, to clear the browser to receive my fitting file.
This is a tedious task, which my right wrist doesn’t like at all. Please create 550 fits for your personal and corporation fits and then delete them all.
@Kadesh_Priestess, no you don’t have to add Singularity support. But could you look into accelerating the import process?
When you open a fit with the all level 5 character and change some skills down to level 4 or lower and then back to level 5 and then open another fit, it keeps the previous lower skill level into account.
What I did was opening my latest talwar and Corax fit in that order and was checking if they would be mwd stable with evasive maneuvering level 4, 3, 2 and capacitor management level 4, 3.
Then I changed them all back to level 5 and opened the Corax fit and it wasn’t mwd stable anymore, so I changed high-speed maneuvering to level 4 and then level 5 again and changed capacitor management to level 4 and 5 again and then it showed the proper level 5 stats.
Windows Defender normally complains that Pyfa comes from an untrusted source but allows me to install it. This time it detected a virus and killed the download
Please scan and sign the code before publishing - we shouldn’t need to play Russian roulette to use the tool!
Signing the code (and having the executable scanned prior to being uploaded) won’t protect you from anything though… there’s nothing stopping the author from adding malicious code, then scanning it, signing it and uploading the Hash so everyone can verify the download they received was the original. Which leaves us (the users) with a couple of options, trust the author, or not
The site advertises as a trusted CA (Certificate Authority), which goes to my point above, if anyone can sign up, get a certificate and start signing their code, is it really secure?
My point being, trust in code, just like in Eve, is built over time. I’ve not seen any issues with the repo (so it’s unlikely the account has been compromised, but not impossible) so will continue to trust the code/executables posted there.
@Kadesh_Priestess There used to be a way you could flag the exe with MS as it showing a false positive, and in the next definition update of the AV it would resolve it, but you may be best served just releasing another ‘update’ to see if it fixes itself. IIRC the heuristics scanner in Defender looks for ‘suspicious’ code behaviour, so depending on where the new logic has been added, and what it touches (or doesn’t) that could account for it.
Edit: Just read the MS docs link posted on the bug page, M$ makes it so simple “Submit the file in question as a software developer. Wait until your submission has a final determination.”
edit: just quickly checked it, and it works for me. Please post detailed scenario here or in linked issue.
The point is, it is the only tool which detected it as a trojan. I’ve got reports next day I released 2.10.1 from my corpmate that executable is flagged. He ran it through virustotal which reported no issues at all. Build process hasn’t changed, changes to python code were trivial. This issue contains some info on how you can review code changes and build process.
As to how to fix it: two obvious solutions are signing the code and changing installer to be MSI.
Signing the code - prior to @elitatwo 's post, I had only info I’ve got from my corpmate, that certificates are quite expensive, like 500 usd/year. While I am quite fond of running Pyfa, I am not going to pay that when there’re, say, cheaper options But as there’s a free option, it makes me to think a little more about it. Build process now becomes the biggest concern. How can I sign pyfa exe and installer exe via these public services (appveyor builds windows releases, travis builds mac) without exposing my private key? I have no idea. Something to look into.
Changing installer to MSI. No idea if it will protect installer from being flagged (and that’s what is being flagged, as far as I understand) and quite an effort, but looks like “cheaper” option than signing the code.
Please understand that I am taking these issues seriously, but given that I have few other projects ongoing (rewriting Phobos - which is used to extract data for Pyfa, as well as doing some research and learning for possible Pyfa rewrite), my regular job, and life outside of IT, I am unsure about timeframe of resolving this issue. This week I will have very little time, but I will try to look into it on the weekend/next week.
September update. Please note that I do not have access to machine with Windows Defender antivirus (as it gets disabled by other AV on machines I have access to), but virustotal shows that installer is clean.
I want to echo this. It’s an incredibly useful tool.
Microsoft released a platform update for Defender a few days ago (KB4052623). Pyfa 2.11 downloaded and installed with no errors - other than the usual untrusted source message.
[Nidhoggur, *Ratting in Provi]
Damage Control II
Drone Damage Amplifier II
Drone Damage Amplifier II
Drone Damage Amplifier II
Drone Damage Amplifier II
Omnidirectional Tracking Link II
Capital Shield Extender II
EM Ward Field II
Capital Shield Extender II
Thermal Dissipation Field II
Drone Navigation Computer II
Networked Sensor Array
Fighter Support Unit I
Fighter Support Unit I
Fighter Support Unit I
Heavy Energy Neutralizer II
Capital Anti-EM Screen Reinforcer II
Capital Anti-Thermal Screen Reinforcer II
Capital Core Defense Field Extender I
But as there’s a free option, it makes me to think a little more about it. Build process now becomes the biggest concern. How can I sign pyfa exe and installer exe via these public services (appveyor builds windows releases, travis builds mac) without exposing my private key? I have no idea. Something to look into.
