Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Promethium]

Hey there! Sorry to be a bother, but was running some of the utilities from the updated pack through Virustotal, and found something different than the usual false positives that are quite common in the LNP: https://www.virustotal.com/gui/file/266167fe87f60ba6d99516689935f1e9bd525286ed4974a152d03c0fa0e74a46

The LegendsViewer is making Virustotal believe it is ransomware (which I've never had happen when scanning any of the previous packs). It even goes as far as to say, in the "view rule" breakdown, that the likelihood of it being a false positive is "unlikely", and classifying it as "critical".

I know false positives aren't exactly rare in previous iterations of the pack and its utilities, but this one was different enough that I felt it was worth letting people know/asking people if they have experienced any issues, or noticed anything strange with said utility.

[Duuvian]

I searched the name of the virus and found along with what appeared to be guides on how to remove it if someone does have it, there also were a few results talking about false positives from the same Maxsecure that flags it in the Virustotal link.

Githubs that had the same issue:
https://github.com/bleachbit/bleachbit/issues/948
https://github.com/lian/msfs2020-go/issues/14

I don't know enough to say 100% it's not a virus but it seems likely to be a false positive.

If that turns out to be the case, here is the link to the Maxsecure submissions page for false positives if that helps PeridexisErrant or other maintainers, I found it on one of those github threads.

https://www.maxsecureantivirus.com/submit_aFalse_Positive.htm

[Ziusudra]

A single hit on VT is almost always a false positive especially if the engine that flagged it is not one of the major engines. None of the major sites that review antivirus engines even mention MaxSecure.

And the sha256 hash on VT matches the file released on https://github.com/Kromtec/LegendsViewer (for the version in this pack). So if it is a trojan, it's a publicly open-sourced one.

Where do you see this "view rule", "unlikely", and "critical"? I don't see that on VT. Is it something you hav to be logged in to see?

[PeridexisErrant]

The Starter Pack has updated to 0.47.05-r06!
As usual, you can get it here.

0.47.05-r06
 - updated Vettlingr graphics to 1.6
 - updated Legends Viewer to 1.20.08
 - removed Meph graphics due to attribution/copyright concerns

SHA256:  74c6dfdca808a0222457e06cf122c1691498229234f6d9769d4a6a601b65ba04

If you want to say thanks, check out Toady's Patreon, or even mine! 

[Promethium]

A single hit on VT is almost always a false positive especially if the engine that flagged it is not one of the major engines. None of the major sites that review antivirus engines even mention MaxSecure.

And the sha256 hash on VT matches the file released on https://github.com/Kromtec/LegendsViewer (for the version in this pack). So if it is a trojan, it's a publicly open-sourced one.

Where do you see this "view rule", "unlikely", and "critical"? I don't see that on VT. Is it something you hav to be logged in to see?

It should appear near the top if you are signed in. Looks like this if you're curious: https://imgur.com/a/B0ORfte

[clinodev]

A single hit on VT is almost always a false positive especially if the engine that flagged it is not one of the major engines. None of the major sites that review antivirus engines even mention MaxSecure.

And the sha256 hash on VT matches the file released on https://github.com/Kromtec/LegendsViewer (for the version in this pack). So if it is a trojan, it's a publicly open-sourced one.

Where do you see this "view rule", "unlikely", and "critical"? I don't see that on VT. Is it something you hav to be logged in to see?

It should appear near the top if you are signed in. Looks like this if you're curious: https://imgur.com/a/B0ORfte

Legends Viewer just updated in the Pack, perhaps it's fixed now.

[Ziusudra]

Yeah, new current version doesn't match that rule.

As for that rule that did match the previous version, it's not dated but the links it mentions are all over a year old - the major engines would pick it up by now. The fact that they don't indicates a false positive. (MaxSecure flags it as a different trojan and isn't a major engine.)

[Rekov]

Is this a change to Vettlingr's tileset? I no longer see the Kruggsmash font in the PyLNP Launcher under Graphics > Customize > Font.

[clinodev]

Is this a change to Vettlingr's tileset? I no longer see the Kruggsmash font in the PyLNP Launcher under Graphics > Customize > Font.

I don't know if it's an oversight, or intentional on vettlingr's part, but I have permission from Kruggsmash to distribute this version.

https://drive.google.com/file/d/1-1aByBHb4AobFuEf0lBP9IAZNeCg7THj/view?usp=sharing

If you save it in:

Code: [Select]

PeridexisErrant's Starter Pack 0.47.05-r05\LNP\graphics\Vettlingr\data\art
it should work as before for you, with the new name. Or you could rename it.

This is the current set Kruggsmash uses, I believe.

[Socran]

So I'm trying to run the launcher but I keep getting this error.

Does anyone know what could be causing this and how to fix it?  I noticed people here talking about having the issue and fixing it just by moving the file to another folder, but that doesn't work for me, and they stopped discussing it before ever figuring out what the actual cause was and what needs to actually be done to fix it.

[TV4Fun]

The version of SoundSense that comes with the starter pack is still the one that includes a sample config that makes almost every sound into a flute. It's easy enough to get around by deleting sample.xml from the packs/default directory, but it would be kind of nice if the starter set already did that.

[thurin]

Time to update the tagline.

"over 2 million downloads and still counting!"

[PeridexisErrant]

The Starter Pack has updated to 0.47.05-r07!
As usual, you can get it here, this time with some lovely new DFHack features 

0.47.05-r07
 - updated DFHack to 0.47.05-r5
 - updated TwbT to 0.47.05-r5 (unofficial build by thurin)

SHA256:  77fa01bd1386468f73a0c10094877b9cd7253283aca44ceca23e9a6bbff01d49

[myk]

It seems like there is a good amount of confusion generated by having two versions of quickfort -- the one in the utilities directory and the newer implementation that comes with DFHack. It might help reduce confusion if they used the same blueprints directory. That way users will have only one place to add blueprints to and it can be read by both quickfort implementations. Would it be possible to move the LNP/utilities/Quickfort/blueprints directory to Dwarf Fortress 0.47.05/blueprints/library/LNPquickfort?

The Quickfort distributed with LNP keeps a state file that determines where the file open dialog looks.  We could point it directly to that directory so LNP Quickfort can still find its blueprints easily. All it would take, I think, is to add a file named LNP/utilities/Quickfort/config/state.ini to the distribution that has the following contents:

Code: [Select]

[GUI]
PlaybackMode=macro
ShowFullTip=1
LastFolder=..\Dwarf Fortress 0.47.05\blueprints\library\LNPquickfort
DoMacroMSCheck=1

Would that be ok?

[Pokcetracket]

Hello, new user to this forum.

My game keeps crashing after ~5 minutes of running a fortress. I'm using TwbT and DFHack. Looking through the stderr and gamelog, there doesn't seem to be a pattern for why it's crashing. How can I begin to debug this or find the cause? Thanks.