The concern around deep fakes is that they could be used to trick people, fair enough, but apparently tricking people doesn’t require much, if any, believably. Throughout history up to today people are tricked by the most obvious untruths with disastrous consequences on large scales.
Readit Newsjamp897 commented on Github restricts public Faceswap repo to logged-in users github.com/deepfakes/face... · Posted by u/jordwalke
jamp897 commented on Podman and Buildah available in RHEL 7.6 and RHEL 8 Beta developers.redhat.com/blo... · Posted by u/siddharthgoel88
It would be nice if this was one tool, rather than two overlapping tools with some incompatiblies between them.
jamp897 commented on Microsoft confirms Bing is down in China techcrunch.com/2019/01/23... · Posted by u/obahareth
jamp897 commented on Microsoft confirms Bing is down in China techcrunch.com/2019/01/23... · Posted by u/obahareth
This actually surprises me for how much effort Microsoft puts into being compliant with China. Last year China took down Yahoo! too, despite Yahoo's relationship with Alibaba.
I was an expat last year and with Google (& DuckDuckGo) blocked I already had pretty few options of search engine. Short of learning enough Chinese to manage Baidu, I can't imagine how hard it would be to use internet as a foreigner in China now.
My AT&T iPhone wasn’t blocked when roaming in China, it seems they make exceptions for foreign phones. They’re censors are very clever at knowing where the limits are.
jamp897 commented on Remote code execution vulnerability in apt/apt-get justi.cz/security/2019/01... · Posted by u/justicz
The situation you described is the same thing that happens with a MITM attack with HTTPS. You would get a failed download from any mirror.
Do you have a response to my question? "Consider, why not double-wrap your stream? Put TLS on top of TLS on top of HTTP?"
It’s not the same, Comcast and other ISPs don’t tamper with HTTPS, and if they break the HTTPS connection then it’s a clearer problem for the ISP to troubleshoot than corruption.
Sorry I don’t understand what double wrapping has to do with it, or why you’d ever do that.
jamp897 commented on Remote code execution vulnerability in apt/apt-get justi.cz/security/2019/01... · Posted by u/justicz
HTTP is the null hypothesis, since it's simpler. Usually there is a great reason to reject this null hypothesis - it prevents security vulnerabilities. But if there is no added value, then there is no reason to do it.
Consider, why not double-wrap your stream? Put TLS on top of TLS on top of HTTP?
Yet it’s actually not simpler for the user, since their transfer can then be tampered with either by accident or intentionally leaving the user with a broken download and then what do they do? A redownlaod from a different mirror makes no difference.
jamp897 commented on Remote code execution vulnerability in apt/apt-get justi.cz/security/2019/01... · Posted by u/justicz
What this might usher in is the era of cryptographically signed news articles. Not just credibility but verifiability. Blocking