FS Protection PC 17.7 releases

Superuser

Re: FS Protection PC 17.7 releases


@yeoldfart wrote:

I run IE beta Version 76.0.176.1 (Official build) dev (64-bit) and do not encounter such problems, it is just a statement I make since IE has a Chromium kernel.


Hello,

 

Sounds that it is Microsoft Edge. At least, if Internet Explorer is not completely rebranded (declined) to fresh Microsoft Edge (Chromium-oriented) with upcoming builds.

 

My current Windows 10 (1903) still with two different browsers: Internet Explorer 11 and Microsoft Edge (44*?).

In fact, with both browsers - F-Secure BP HTTPS support is not available on current time. With Microsoft Edge by default, with Internet Explorer by enabled EPM option.

 

I did not try "fresh" Microsoft Edge (beta) yet. Maybe, there are improvements - but I still think that for HTTPS Support need to install F-Secure BP extension (otherwise - noted functionality is not available). Perhaps, beta Microsoft Edge with support for Google Chrome extensions by default (and as a result - proper state for HTTPS Support functionality of F-Secure BP).

 

Thanks!

 

Superuser

Re: FS Protection PC 17.7 releases

you are right it's edge
Superuser

Re: FS Protection PC 17.7 releases

for your further info I simply got it from there https://chrome.google.com/webstore/detail/browsing-protection and it works like a charm.

Highlighted
Superuser

Re: FS Protection PC 17.7 releases

Sounds that URL is redacted (as a result "Page not found"). But, yes, it is known place for "Google Chrome" addon (fs protection Settings tab "Browsing Protection" with this information).

I, usually, used it for browsers like Opera.

F-Secure

Re: FS Protection PC 17.7 releases

Release 17.7 beta 5 (4.20.2816):

 

Known issues:

  • The About page is missing some localization strings, should be fixed in the coming release

Fixed issues:

  • Values on the Support tab are not visible on some languages if narrow (PBL-5321)
  • Main UI browser extension "Set up now" link to help broken (PBL-5310)
  • Scheduled scan for "each month" launched each week (SAFE_BUG-02791, PBL-5306)
  • A setting can be changed without administrator rights – misleading "Edit settings" explanation (PBL-5303)
  • The blank Account ID is shown if subscription code is not entered yet (PBL-5297)
  • Cannot paste characters in Proxy setting field (SAFE_BUG-02787, PBL-5293)
  • The Subscription valid date is still showing after the expiration (PBL-5281)
  • Subscription valid date 1.1.1970 if the subscription code was not entered yet (PBL-5279)
  • Wrong subscription valid until date if no expiration date (PBL-5273)
  • The Proxy Address value does not take effect properly (PBL-5262)
  • New help button has ugly focus rectangle (PBL-5261)
  • Hover effect on selected settings tab not working (PBL-5257)
  • LOC: "Support" string is not localized yet. (SAFE_BUG-02786, PBL-5243)
  • Small alignment issues with "shield" icon in Settings (PBL-5239)
  • Small alignment issues with toggle switch in Settings (PBL-5238)
  • Unnecessarily alarming scheduled scan result for PUA in scanning report (PBL-5231)
  • "Subscription is about to expire" window is shown after the expiration, log out and restart (PBL-5215)
  • "You are not yet protected" is not showing after log out if expired (PBL-5213)
  • Some focus issues in Settings (PBL-5202)
  • Web pages of "illegal" category should be blcoked by default (PBL-5201)
  • SAFE 17.6 continuously reports malfunction (PBL-5134)
  • Misleading name for DeepGuard detections counter (PBL-5113)
  • New Settings UI, time control does not support 12-hour clock (PBL-4957)
F-Secure

Re: FS Protection PC 17.7 releases

Release 17.7 beta 6 (4.20.3102):

Fixed issues:

  • "Check for updates" from system tray does not trigger update (PBL-5363)
  • Scheduled scan start time hours field does not allow one digit numbers (PBL-5334)
  • Usability problem with scheduled scanning control hours field (PBL-5332)
  • Settings Window crashes when you change scheduled scan time (PBL-5327)
  • SAPC 17.6 - SAFE on SAFE reinstall flow is broken (PBL-5326)
  • User Port value vanishes if you edit the address (PBL-5325)
  • Help button shows "help not available" page (PBL-5319)
  • Unnecessarily alarming scheduled scan result for PUA (PBL-5231)
  • Log out SAFE account improvement (PBL-5173)
  • SAFE 17.6 continuously reports malfunction (PBL-5134)
  • Misleading title for DeepGuard detections counter (PBL-5113)
  • Missing Information for Protection Logout Window (PBL-5068)
F-Secure

Re: FS Protection PC 17.7 releases

Release 17.7 beta 7 (4.20.3453):

Fixed issues:

  • Inaccurate AM/PM value location on the Scheduled scanning area (PBL-5421)
  • Banking protection session does not start with https://www.poste.it/ (PBL-5418)
  • Parental Control is not currently working as expected (PBL-5391)
  • Log out confirmation dialog has wrong, non-customized icon (PBL-5383)
  • Banking Protection doesn't trigger consistently for https://bank.smile.co.uk/ (PBL-5371)
  • Ing.de and Paypal.de in Chrome, when it comes to Banking Protection (PBL-5370)
  • Check for updates from system tray does not trigger update (PBL-5363)
  • The Support Tool instruction in Help does not match with the actual UI (PBL-5260)
  • Scan Option "Every four weeks" is not described in Help (PBL-5259)
  • The Help button is located differently on different Settings tabs (PBL-5254)
  • Change the Help page which opens from the Notifications tab with F1 (PBL-5140)
  • Disable the "Full screen maximize" button for the Logout pop-up (PBL-5045)
F-Secure

Re: FS Protection PC 17.7 releases

Release 17.7 beta 8 (4.20.3560):

Fixed issues:

  • .NET missing dialog text is truncated (PBL-5333)

  • Ransomware protection doesn't work (PBL-5426)

Patron

Re: FS Protection PC 17.7 releases

Please, educate me: How can a basic user tell if Ransomware pårotection is working or is not working?

F-Secure

Re: FS Protection PC 17.7 releases

Hi @martink 

 

It's not easy to test if it's working or not, since the algorithm that triggers it is quite complicated, so I can't give you any good advice on that. We accidentally broke it in beta 7 and didn't notice it immediately, but our automated tests flagged it.

 

Ville

(F-Secure R&D)