4 ms·

I saw somewhere on Twitter, possibly as a reply to Scott Helme, that they possibly added these URLs to their CSP because they were getting errors in their CSP l

I saw somewhere on Twitter, possibly as a reply to Scott Helme, that they possibly added these URLs to their CSP because they were getting errors in their CSP logs from machines that had adware/malware loaded. Can't find the tweet though, so maybe it wasn't him (but I'm reasonably sure it was a discussion of CSP, ReportURI, and the fact the CSP changes depending on logged in/out of zoom's site). Pretty bad solution if that was indeed the case.

sebazzz 7y ago
Ah, the classic "fix it just to shut the error up" without actually looking at the cause. Lowest bidder contractor probably.
- philsnow 7y ago
  I had some audio issues today on a zoom and they helpfully asked for me to sudo to fix the problem https://i.imgur.com/oCqmZZ3.png https://i.imgur.com/oCqmZZ3.png "just to shut the error up" is about right.
  - youareostriches 7y ago
    Actually, killing coreaudiod can be necessary every once in a while.
  - drwl 7y ago
    what version of macos are you using?
  - ac29 7y ago
    Its amazing how many Zoom screenshots have spelling or grammar errors, like this one. For a supposedly US based company, its pretty clear a lot of the UI text isn't written by a native English speaker. I'm not intedning to demean non-native English speakers or their ability to write code - but this looks pretty bad from a QA standpoint. edit: elsewhere in the thread its shown most of the software engineering team is in China, which explains this.
- bink 7y ago
  Having worked with CSP this isn't really something that can be fixed. If you disable scripts from all but approved sources your reporting URI will be flooded with reports from browser extensions and malware trying to inject code. The best you can do is silence the reports after they arrive (or in this case just allow them, yuck).
  - amenghra 7y ago
    You are supposed to set a strict policy and disable the reporting. Reporting is for dev/debugging purpose, it’s not meant to be the end state.

sebazzz 7y ago

Ah, the classic "fix it just to shut the error up" without actually looking at the cause. Lowest bidder contractor probably.

philsnow 7y ago
I had some audio issues today on a zoom and they helpfully asked for me to sudo to fix the problem https://i.imgur.com/oCqmZZ3.png https://i.imgur.com/oCqmZZ3.png "just to shut the error up" is about right.
- youareostriches 7y ago
  Actually, killing coreaudiod can be necessary every once in a while.
- drwl 7y ago
  what version of macos are you using?
- ac29 7y ago
  Its amazing how many Zoom screenshots have spelling or grammar errors, like this one. For a supposedly US based company, its pretty clear a lot of the UI text isn't written by a native English speaker. I'm not intedning to demean non-native English speakers or their ability to write code - but this looks pretty bad from a QA standpoint. edit: elsewhere in the thread its shown most of the software engineering team is in China, which explains this.
bink 7y ago
Having worked with CSP this isn't really something that can be fixed. If you disable scripts from all but approved sources your reporting URI will be flooded with reports from browser extensions and malware trying to inject code. The best you can do is silence the reports after they arrive (or in this case just allow them, yuck).
- amenghra 7y ago
  You are supposed to set a strict policy and disable the reporting. Reporting is for dev/debugging purpose, it’s not meant to be the end state.