Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de), page 13

  1. U+039b (u039b@mastodon.social)'s status on Friday, 19-Jan-2018 07:15:59 EST U+039b U+039b

    ⚠️ Dark Caracal has trojanized Orbot, Signal, WhatsApp and other Android applications to exfiltrate files, contacts, messages and more.

    More details in the Lookout - EFF report: https://info.lookout.com/rs/051-ESQ-475/images/Lookout_Dark-Caracal_srr_20180118_us_v.1.0.pdf

    https://mastodon.social/media/pZHO-kEyTYG1W295KjA

    In conversation Friday, 19-Jan-2018 07:15:59 EST from mastodon.social permalink Repeated by rugk
  2. Nuntius (nuntius@mastodon.club)'s status on Friday, 19-Jan-2018 08:41:16 EST Nuntius Nuntius
    in reply to
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk

    @rugk Aber vielleicht sollten wir lieber nicht zu viel Staub aufgewirbeln solange an der Sache eigentlich noch nichts dran ist...

    https://m.heise.de/newsticker/meldung/Meltdown-und-Spectre-Vermutlich-Scherze-mit-spekulativen-Angriffen-Skyfall-und-Solace-3946313.html

    In conversation Friday, 19-Jan-2018 08:41:16 EST from mastodon.club permalink Repeated by rugk
  3. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Friday, 19-Jan-2018 08:49:30 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Nuntius
    @nuntius Hehe, ja sicher kann das ein Witz sein. Mal schauen…
    In conversation Friday, 19-Jan-2018 08:49:30 EST from gnusocial.de permalink
  4. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Friday, 19-Jan-2018 05:34:09 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    in reply to
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    Aber so wie es aussieht (im wörtkl. Sinne), betrifft Skyfall wohl nur Intel… https://skyfallattack.com/favicon.ico
    In conversation Friday, 19-Jan-2018 05:34:09 EST from gnusocial.de permalink
  5. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Friday, 19-Jan-2018 05:30:59 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    in reply to
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    Die Icons bewerte ich schon mal als verbesserungswürdig… https://solaceattack.com/favicon.ico https://skyfallattack.com/favicon.ico
    In conversation Friday, 19-Jan-2018 05:30:59 EST from gnusocial.de permalink
  6. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Friday, 19-Jan-2018 05:30:28 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    Spectre/Meltdown do not have ended yet…  https://solaceattack.com/ and https://skyfallattack.com/ #solace #skyfall
    In conversation Friday, 19-Jan-2018 05:30:28 EST from gnusocial.de permalink
  7. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Thursday, 18-Jan-2018 15:50:16 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • jomo :verified:
    @jomo Sure… :)
    In conversation Thursday, 18-Jan-2018 15:50:16 EST from gnusocial.de permalink
  8. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Thursday, 18-Jan-2018 15:47:50 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • jomo :verified:
    @jomo It's up for me.
    In conversation Thursday, 18-Jan-2018 15:47:50 EST from gnusocial.de permalink
  9. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Thursday, 18-Jan-2018 14:11:34 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • OpenStreetMap
    Compare !osm from now and 10 years ago… Very impressive!

    https://mvexel.github.io/thenandnow/#10/52.2644/5.2899 https://gnusocial.de/attachment/4787855
    In conversation Thursday, 18-Jan-2018 14:11:34 EST from gnusocial.de permalink
  10. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Thursday, 18-Jan-2018 13:17:12 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Thomas :Anoxinon:
    @thomas Gerade auf Wikipedia (https://de.wikipedia.org/wiki/Heartbleed) gesehen…

    "Die Schwedische Metalcore-Band The Unguided widmete dem Heartbleed-Bug auf ihrem Album "And the Battle Royale" ein Lied."

    Na, schon gewusst? 😅
    In conversation Thursday, 18-Jan-2018 13:17:12 EST from gnusocial.de permalink
  11. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 16:48:34 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    Despite the sad trigger a good read about the story behind SecureDrop. E.g. did not knew it is so old… (considering it has been adopted by major news portals only recently.)

    https://gnusocial.de/url/4753824
    In conversation Tuesday, 16-Jan-2018 16:48:34 EST from gnusocial.de permalink

    Attachments

    1. A tribute to James Dolan, co-creator of SecureDrop, who has tragically passed away at age 36
      In memory of computer security expert James Dolan, 1981-2017. 
  12. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 16:29:53 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    in reply to
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    (actually the better header would be "no e2e crypto")
    In conversation Tuesday, 16-Jan-2018 16:29:53 EST from gnusocial.de permalink
  13. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 16:29:19 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Verschlüsselung
    Apple, e2e crypto and China – what could possibly go wrong? (Spoiler: we don't know whether something it's wrong – and this is, actually, the problem.)

    https://blog.cryptographyengineering.com/2018/01/16/icloud-in-china/


    !verschluesselung 
    In conversation Tuesday, 16-Jan-2018 16:29:19 EST from gnusocial.de permalink

    Attachments

    1. iCloud in China
      By Matthew Green from A Few Thoughts on Cryptographic Engineering

      Last week Apple made an announcement describing changes to the iCloud service for users residing in mainland China. Beginning on February 28th, all users who have specified China as their country/region will have their iCloud data transferred to the GCBD cloud services operator in Guizhou, China.

      Chinese news sources optimistically describe the move as a way to offer improved network performance to Chinese users, while Apple admits that the change was required by new Chinese regulations on cloud services. Both explanations are almost certainly true. But neither answers the following question: regardless of where it’s stored, how secure is this data?

      Apple offers the following:

      Apple has strong data privacy and security protections in place and no backdoors will be created into any of our systems,” it says.

      Well that’s nice.

      But what, precisely, does it mean? If Apple is storing user data on Chinese services, we have to at least accept the possibility that the Chinese government might wish to access it — and possibly without Apple’s permission. Is Apple saying that this is technically impossible?

      The answer, as you might have guessed, probably comes down to encryption.

      Does Apple encrypt your iCloud backups?

      Unfortunately there are many different answers to this question, depending on which part of iCloud you’re talking about, and — ugh — which definition you use for “encrypt”. The dumb answer is the one given in the chart on the right: all iCloud data probably is encrypted. But that’s the wrong question. The right question is: who holds the key(s)?

      This kind of thing is Not Helpful.

      There’s a pretty simple thought experiment you can use to figure out whether you (or a provider) control your encryption keys. I call it the “mud puddle test”. It goes like this:

      Imagine you slip in a mud puddle, in the process (1) destroying your phone, and (2) developing temporary amnesia that causes you to forget your password. Can you still get your iCloud data back? If you can (with the help of Apple Support), then you don’t control the key.

      With one major exception — iCloud Keychain, which I’ll discuss below — iCloud fails the mud puddle test. That’s because most Apple files are not end-to-end encrypted. In fact, Apple’s iOS security guide is clear that it sends the keys for encrypted files out to iCloud.

      But there’s a wrinkle. And that is: iCloud isn’t entirely an Apple service, even here in the good-old U.S.A. In fact, the vast majority of iCloud data is not actually stored by Apple at all. Every time you back up your phone, your (encrypted)

      A list of HTTPS requests made during an iCloud backup from an iPhone. The bottom two addresses are Amazon and Google Cloud Services “blob” stores.

      data is actually transmitted directly to a variety of third-party cloud service providers including Amazon, Google and Microsoft.

      And this is, from a privacy perspective, mostly fine! (With some caveats!**) Those services act merely as “blob stores”, storing unreadable encrypted data files uploaded by Apple’s customers. At least in theory, Apple still controls the encryption keys for that data, hopefully on a server in a dedicated Apple datacenter.*

      So what exactly is Apple storing in China?

      Good question!

      You see, it’s entirely possible that the new Chinese cloud stores will perform the same task that Amazon AWS, Google, or Microsoft do in the U.S. That is, they’re storing useless encrypted blobs of data that can’t be decrypted without first contacting the iCloud mothership back in the U.S. That would at least be one straightforward reading of Apple’s announcement, and it would also be the most common sense mapping between iCloud’s current architecture and whatever it is Apple is doing in China.

      Of course, this interpretation seems hard to swallow. In part this is due to the fact that some of the new Chinese regulations appear to include guidelines for user monitoring. I’m no lawyer, and certainly not an expert in Chinese law — so I can’t tell you if those would apply to backups. But it’s at least reasonable to ask whether Chinese law enforcement agencies would accept their total ability to access this data without phoning home to Cupertino, not to mention Apple’s ability to wipe all Chinese accounts. Solving these problems would require that Apple store keys as well as data on the Chinese mainland.

      The critical point is that these two interpretations are not compatible. One implies that Apple is simply doing business as usual. The other implies that they may have substantially weakened the security protections of their system — at least for Chinese users.

      And here’s my problem. If Apple needs to fundamentally rearchitect iCloud to comply with Chinese regulations, that’s certainly an option. But they should say explicitly and unambiguously what they’ve done. If they don’t make things explicit, then it raises the possibility that they could make the same changes for any other portion of the iCloud infrastructure without announcing it.

      It seems like it would be a good idea for Apple just to clear this up a bit.

      You said there was an exception. What about iCloud Keychain?

      I said above that there’s one place where iCloud passes the mud puddle test. This is Apple’s Cloud Key Vault, which is currently used to implement iCloud Keychain. This is a special service that stores passwords and keys for applications, using a much stronger protection level than is used in the rest of iCloud. It’s a good model for how the rest of iCloud could one day be implemented.

      For a description, see here. Briefly, the Cloud Key Vault uses a specialized piece of hardware called a Hardware Security Module (HSM) to store encryption keys. Users can access their own keys only if they know their iCloud Keychain password — which is typically the same as the PIN/password on your iOS device. However, if anyone attempts to access this data too many times without knowing the right password, the stored keys get wiped.

      The important thing is that the above applies even to Apple themselves. In short: Apple has designed a key vault that even they can’t be forced to open. Only customers can open it.

      What’s strange about the recent Apple announcement is that users in China will apparently still have access to iCloud Keychain. This means that either (1) at least some data will be totally inaccessible to the Chinese government, or (2) Apple has somehow weakened the version of Cloud Key Vault deployed to Chinese users. The latter would be extremely unfortunate, and it would raise even deeper questions about the integrity of that system.

      Probably there’s nothing weird going on, but this is an example of how Apple’s vague (and imprecise) explanations make it harder to trust their infrastructure around the world.

      So what should Apple do?

      Unfortunately, the problem with Apple’s disclosure of its China’s news is, well, really just a version of the same problem that’s existed with Apple’s entire approach to iCloud.

      Where Apple provides overwhelming detail about their best security systems (file encryption, iOS, iMessage), they provide distressingly little technical detail about the weaker links like iCloud encryption. We know that Apple can access and even hand over iCloud backups to law enforcement. But what about Apple’s partners? What about keychain data? How is this information protected? Who knows.

      This vague approach to security might make it easier for Apple to brush off the security impact of changes like the recent China news (“no backdoors!”) But it also confuses the picture, and calls into doubt any future technical security improvements that Apple might be planning to make in the future. For example, this article from 2016 claims that Apple is planning stronger overall encryption for iCloud. Are those plans scrapped? And if not, will those plans fly in the new Chinese version of iCloud? Will there be two technically different versions of iCloud? Who even knows?

      And at the end of the day, if Apple can’t trust us enough to explain how their systems work, then maybe we shouldn’t trust them either.

      Notes:

      * This is actually just a guess. Apple could also outsource their key storage to a third-party provider, even though this would be dumb.

      ** A big caveat here is that some iCloud backup systems use convergent encryption, also known as “message locked encryption”. The idea in these systems is that file encryption keys are derived by hashing the file itself. Even if a cloud storage provider does not possess encryption keys, it might be able to test if a user has a copy of a specific file. This could be problematic. However, it’s not really clear from Apple’s documentation if this attack is feasible. (Thanks to RPW for pointing this out.)

  14. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 16:11:04 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Verschlüsselung
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    Der Moment, wenn du dir die neuste Sicherheitslücke anschauen/verstehen willst und heraus findest, dass du dir die schon vor einem halben Jahr angeschaut hast… 😊

    @rugk
    https://gnusocial.de/notice/13118439 !verschluesselung 
    In conversation Tuesday, 16-Jan-2018 16:11:04 EST from gnusocial.de permalink

    Attachments

    1. Tue Jan 16 21:55:42 +0100 2018 (Qvitter)
      By rugk (rugk@gnusocial.de) from GNUsocial.de
      BTW, the news just going around the group chat vulnerabilities in major crypto protocol were public in July 2017 (see my own summary below; which is still valid AFAIK). Good explanation on https://www.wired.com/story/whatsapp-security-flaws-encryption-group-chats/

      Seems news outlets need talks (RealWorldCrypto in Swizerland) to notice such things… :)
      And authors seem to revised their paper in 2018, too.

      @rugk
      https://gnusocial.de/notice/10788447 !threema 
  15. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 15:55:42 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Threema
    • rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    BTW, the news just going around the group chat vulnerabilities in major crypto protocol were public in July 2017 (see my own summary below; which is still valid AFAIK). Good explanation on https://www.wired.com/story/whatsapp-security-flaws-encryption-group-chats/

    Seems news outlets need talks (RealWorldCrypto in Swizerland) to notice such things… :)
    And authors seem to revised their paper in 2018, too.

    @rugk
    https://gnusocial.de/notice/10788447 !threema 
    In conversation Tuesday, 16-Jan-2018 15:55:42 EST from gnusocial.de permalink

    Attachments

    1. WhatsApp Flaws Could Allow Snoops to Slide Into Group Chats
      from WIRED
      German researchers say that a flaw in the app's group-chat feature undermines its end-to-end encryption promises.
    2. File without filename could not get a thumbnail source.
      Fri Jul 28 15:54:57 +0200 2017 (Qvitter)
      By rugk (rugk@gnusocial.de) from GNUsocial.de
      More is Less: How group chats weaken the security of instant messengers #Signal, #WhatsApp and !threema https://eprint.iacr.org/2017/713.pdf

      TL;DR: Attackers can often rewind members of group to previous state (replay attack), WhatsApp can add arbitrary users and thus circumvent #e2e crypto in all group chats easily.

      BTW: #Threema fixed the issues, WhatsApp ignored, Signal wants to introduce a new protocol in the future.

      /cc !verschluesselung
  16. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 15:20:33 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Verschlüsselung
    Elliptical curves explained… (in an easy understandable way)  https://www.youtube.com/watch?v=NF1pwjL9-DE !verschluesselung 
    In conversation Tuesday, 16-Jan-2018 15:20:33 EST from gnusocial.de permalink

    Attachments

    1. Elliptic Curves - Computerphile
      By Computerphile from YouTube
  17. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 14:17:12 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • Nuntius
    @nuntius Hmm okay against Apple is strange. Against Intel (which is also done in the US) might be another thing, if you can really say they neglected security…
    In conversation Tuesday, 16-Jan-2018 14:17:12 EST from gnusocial.de permalink
  18. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Tuesday, 16-Jan-2018 13:13:10 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    BTW: Why on hell does GitHub show my commits as signed when I edit them via the web interface? (And no I did not upload my private key… :D ) https://gnusocial.de/attachment/4779344
    In conversation Tuesday, 16-Jan-2018 13:13:10 EST from gnusocial.de permalink
  19. Nuntius (nuntius@mastodon.club)'s status on Tuesday, 16-Jan-2018 07:04:21 EST Nuntius Nuntius
    • Alex (inactive) 🔏

    @lx It's probably gonna be some time until we see fixes. Spectre's apparently hard to exploit, but also hard to fix:

    See http://kroah.com/log/blog/2018/01/06/meltdown-status/
    TLDR: Numerous patches on the mailing lists, some don't even build, kernel devs worked on #Meltdown first, had no real info in #Spectre, no upstream fixes yet

    In conversation Tuesday, 16-Jan-2018 07:04:21 EST from mastodon.club permalink Repeated by rugk
  20. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Sunday, 14-Jan-2018 15:07:34 EST rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    • rtsn
    • Wim 🅾
    • Krister Löfgren
    @wimv12e @rtsn @tardigrader LOL, okay, but at least something… Okay, people could not take it for real (but just for "in-film" story), but it is as far as I see meant to be "real quote" asa hook for the show.
    In conversation Sunday, 14-Jan-2018 15:07:34 EST from gnusocial.de permalink
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.