FSAVCS causes SSL/TLS errors during Visual Studio login, need to find policy item to change.

etomcat

Dear All,

If the presence of F-Secure Client Security 12.3 causes SSL/TLS errors upon Microsoft Visual Studio Express login attempt on some computers, what could be the policy item difference causing this?

 

I only know the problem occurs on schoolroom computers with a generally "stricter" policy set, while teachers' computers with a more relaxed policy work fine. The sysadmin doesnt't want to relax PCs used by pupils and wishes to find a pinpoint solution or a settings change instead.

 

Thanks in advance, Yours Sincerely:

Tamas Feher, Hungary.

Vad

Hello Tamas,

 

There could be several reasons for such issues. Is it acceptable for you to provide to our support fsdiags from teacher's computer and from pupil's computer for checking?

 

Best regards,

Vad

etomcat

Dear Vad,

 

The customer's sysadmin alleges the Microsoft Visual Studio login TLS connection error is caused by engaging the "Adult category - disallowed" setting under Browsing Protection, as seen in the attached screenshots.

 

Permitting access to adult content category makes the problem go away. P0rn however, cannot be allowed on student-use computers for legal reasons, so please suggest a solution for this weird situation.

 

Thanks in advance, Yours Sincerely: Tamas Feher, Hungary.

 

***********************

 

 

Ben

Hello Tamas, 

Would you happen to know where does the Visual studio login goes ?

If not please submit an fsdiag to our labs so we can retrieve the URL that is wrongly rated as adult and correct its rating. 

etomcat

 

Dear Ben,

 

The customer's sysadmin reported they needed to add "visualstudio.com" to Trusted Sites list to solve the problem, so that should be the site producing a false "Adult" blocking.

 

Yours Sincerely: Tamas Feher, Hungary.

Ben

Hi Tamas, 

 

I reported that to our Lab. I'll keep you updated.

Ben

Hi Tamas,

 

Some child urls at visualstudio had indeed some incorrect ratings. They have now been adjusted. 

Please flush the ORSP cache and try again with your customer.