Jump to content


  • Content Count

  • Joined

  • Last visited

About DLF-FG

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello yellowsub, Thanks for letting me know, as it turns out Kaspersky NEVER fixed the false positive, it's only taken them 21 days to get them to fess up! What Kaspersky Lab Technical Support wrote/said: Wed 26-December-2018, 10:56 [they (the "experts") have informed us (Kaspersky Lab Technical Support Level ?) that the issue has been fixed as the detection was a false positive.] has now changed to: Thursday, 17 January 2019 17:59: Initially the (Kaspersky "experts") did replicate the issue, a subsequent test they (the Kaspersky "experts") didn’t replicate the issue therefore, they (the Kaspersky "experts" concluded that its(sic) seems the issue is resolved) NO, the issue: “[KTS19(d)] detecting Brave Installer as malware: PDM:Trojan.Win32.Generic”,is NOT resolved , as all [Brave/Kaspersky] users affected by this issue know only too well. They (Kaspersky Lab Technical Support) frequently "mis-speak", make dubious conclusions and appear oblivious to & unconcerned about/by the consequences to Kaspersky Customers. & of course, because their test methodology is highly suspect & they deny there’s an issue, it’s up to us [Brave/Kaspersky] users, to prove it to them again! Even when we do provide dna proof they engage in the same ground-hog-day-merry-go-round, "there's nothing wrong with Kaspersky sfw, it's due to you/Brave/G_d", anything but K sfw Malawarebytes fixed detecting [Brave Installer as malware: PDM:Trojan.Win32.Generic] in 1 (ONE) day, BECAUSE they totally knew it was/is a false positive... Wonder how long it will take Kaspersky to "twig"? Back to the drawing board....
  2. (I know you're using K "free", not sure which free product or version, how If you chk [your version] you shuld have a [Manage applications], filter on [Brave, expand >[Brave SFW INC] x 2, you'll see [K-your version] has learnt & applied [Trusted] status: however, if you strip your system of [Brave], entirely, you'll find, the issue remains, has not been fixed, is replicable. If, like me, you do not wish to do this, given, Kaspersky experts advised they'd fixed the issue as it was a [false positive] & as [Brave uses] we'd all like to use [Brave] without having a masters degree in "analysing" Kaspersky caused issues and enduring the gruelling ground-hog-day "re-convincing" Kaspersky Lab Technical Support "the fixed issue has not been fixed" sigh, what-life
  3. Yellowsub - yes, it is so annoying, especially as Kaspersky Lab Technical Support advised they'd fixed it: [From: Kaspersky Lab Support Sent: Wednesday, 26 December 2018 10:56 quote: "the issue has been fixed, the detection was a false positive."] I've re-logged the issue with Kaspersky, ref# INC000010042789. I'd encourage every Kaspersky/Brave user "impacted" with this specific issue to also log an INC. I too can perform the Brave update by exiting KTS19, the point is: None of use should have to perform "manual" interventions when the lab have advised they've "fixed the issue". INC000010042789[Brave] update [KTS19] detection[PDM Trojan.Win32.Generic].txt
  4. DLF-FG

    KISA MR19

    Hi Virus_900, Thanks for that, Kaspersky need to urgently implement KISA "export settings", KISA "pause", KISA "exit" functions. All of these functions are available on all other Kaspersky products. The lack of KISA "export settings", means EVERY TIME KISA is removed all config settings are lost. Kaspersky support frequently ask Customers to remove KISA when there are issues & bugs, testing etc are required. Loosing all blocked numbers/settings etc is pre-historic. Why Kaspersky doesn't make basic functionality across ALL products is incomprehensible.
  5. Yes, yellowsub After months of denial Kaspersky Lab Technical Support have advised: From: Kaspersky Lab Support Sent: Wednesday, 26 December 2018 10:56 quote: "the issue has been fixed, the detection was a false positive."
  6. kojo+oi From: Kaspersky Lab Support Sent: Wednesday, 26 December 2018 10:56 quote: "the issue has been fixed as the detection was a false positive."
  7. DaanW, , sorry, you're absolutely right iOS KSB is not the same as KISA [https://www.kaspersky.com.au/internet-security][laptop, desktop or Android mobile]. I've just looked thru 60 pages of Kaspersky support & cannot find the [iOS] commentary I've previously read. Given what you are experiencing I'm beginning to think it may have said there is no KIS for iOS. https://support.kaspersky.com/14349#block4 - no iOS However, https://www.kaspersky.com/security-cloud - Kaspersky Security Cloud, works on iOS. Why not install the Kaspersky Security Cloud free version & test it out before you fork out any $? Caution - with all of Kaspersky's free versions, some features do not work, guess that's how they get people to subscribe... If the "sales guy" was a Kaspersky sales guy I'd complain, otherwise, (Murphy's Law) "never believe anything anyone tells you when they're selling anything!"
  8. KTS19(b) W10x64 1809, Firefox 64.0 Since patch d - Firefox @ startup always requires FF master password to be entered to use FF. 1. Kaspersky Anti-Virus Personal Root Certificate - in Firefox, is installed. 2. [reinstall a certificate for a browser][certificate to Mozilla Firefox][https://support.kaspersky.com/common/error/other/14396?cid=KTS_19.0&utm_source=interceptor&utm_medium=product&utm_campaign=KTS_19.0#block5] instructions do not work 3. Turning off encrypted connections scanning is NOT an acceptable solution. 4. Selecting [Use Windows Certificate Store - recommended] for Mozilla Firefox & Thunderbird defies logic. 5. *****Multiple Kaspersky users are complaining about this universal issue, not device specific, not location specific***** As a secondary issue: a) What is the point/purpose of [Scan secure traffic in Mozilla applications][Use Windows Certificate Store]? b) Why is the [Use Windows Certificate Store] even in application [Network Settings][Mozilla Firefox & Thunderbird] section?
  9. DaanW [https://itunes.apple.com/us/app/id723879672?mt=8] may help, note it does say from [Kaspersky Lab UK Limited]. I don't use iOS so not sure if this will be an issue. Also, I've seen plenty of Kaspersky advice, in their KISA doco stating "...blah, blah, blah > does not work on iOS", so I'd refer to their doco if you find parts of the software not working.
  10. DLF-FG

    KISA MR19

    Does anyone know the release date of KISA MR19?
  11. Also, This may help: [How to set up Kaspersky Safe Kids] https://support.kaspersky.com/12265#block1 to block8 [How to limit device use] https://support.kaspersky.com/12265#block3
  12. Thanks indio, I've already taken all the "recommended" actions for the critical vulnerabilities. All that did was "identify" that the "recommended" solution only partially worked - back to the drawing board Kaspersky! I do worry, not only for myself, but, for all Kaspersky users who think the "best thing since sliced bread" security solution is "looking after things", completely unaware there are critical vulnerabilities in their systems that require action. Implementing "vulnerability scan detection" "notify" events, to the Kaspersky Main Application window & the Notification Centre is a simple fix, it's not like the functionality does not already exist. It could be implemented and shipped with the next patch. It's not a "nice to have", it's essential. Ludicrous really, considering Kaspersky is writing articles of import such as: https://www.kaspersky.com/enterprise-security/wiki-section/products/fileless-threats-protection and at the same time, not doing everything to support their customers.
  13. KTS19,, W10x64. As per Kaspersky Lab Technical Support, it is "by design" that Vulnerability Scan detections, are not "alerted" to Kaspersky users via the Kaspersky main application window, nor the Kaspersky Application Notifications Centre, rather, Kaspersky users are only made aware of these detections when they stumble upon them in Kaspersky Reports or visible notifications. This is despite the fact that (specifically, in this case) the detections have a CVSS Critical rating of 10 - the highest severity. All other scan detections register a visible "alert" on the Kaspersky main application window and in the Kaspersky Notification. It makes no sense that consistency, i.e. alerts for, all scans, for detected objects, is not applied across all Kaspersky products How incomprehensible that a leading security software provider would think alerting their customers to minor recommendations is of any help, while at the same time, burying serious vulnerabilities, so that, only those who go digging/reviewing their security software will find detections. This is a serious flaw in Kaspersky products. Note, in the image, the 2 "recommendations" are for minor adjustments.
  14. Hello Indio, Thanks for replying. Hidden notifications aren't captured in App "Reports". I escalated to Technical Support who've advised: Your statement is correct: "The "Detailed Reports" drop down does not have a "Hidden" category, therefore no way of seeing "Hidden" notifications." "We will escalate the request; as to suggest if future builds of the application can be designed where such an option is available". INC000009562614 Cheers.

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.