Steven Englehardt

@s_englehardt

CS PhD student at Princeton. Working to make the web more private.

Beigetreten April 2014

Tweets

Du hast @s_englehardt blockiert

Bist du sicher, dass du diese Tweets sehen willst? Das Ansehen von Tweets wird @s_englehardt nicht entblocken.

  1. hat retweetet
    12. Feb.

    never seen this before: Salon now offers to "suppress ads" if you lease out your PC's "unused computing power" 🤔

    Rückgängig machen
  2. hat retweetet
    8. Feb.

    🔐⚠️ The moment we've all been waiting for! Chrome will mark all HTTP sites as "Not secure" in July 2018. 🔐⚠️

    Diesen Thread anzeigen
    Rückgängig machen
  3. 5. Feb.

    [7/7]This is surprisingly similar to the leaks we found to be caused by session replay scripts (). These scripts also scrape user data from the DOM and use a blend of automated & manual redaction. As highlighted in the post, sensitive data leaks are common.

    Diesen Thread anzeigen
    Rückgängig machen
  4. 5. Feb.

    [6/7]The effort spent by a publisher to ensure no sensitive data is collected could just as well be spent explicitly choosing the form fields from which to collect data. The latter whitelist approach is also significantly less likely to lead to unexpected leaks.

    Diesen Thread anzeigen
    Rückgängig machen
  5. 5. Feb.

    [5/7]Mixpanel offers sites a way to further redact user inputs. This might seem to solve the issue, but it's directly at odds with the selling point of the product: to make it dead simple to gather form analytics at any time.

    Diesen Thread anzeigen
    Rückgängig machen
  6. 5. Feb.

    [4/7]This shouldn't be thought of as a bug! Instead, it adds to the evidence that the automated scraping of user data from a page is an inherently insecure process. There is no way a heuristic-based blacklist will be able to filter all possible sensitive information leaks.

    Diesen Thread anzeigen
    Rückgängig machen
  7. 5. Feb.

    [3/7]In this specific case, the React library was handling passwords in a way the heuristic didn't account for. Mixpanel's announcement also hints that similar leaks may have occurred from password manager extensions changing the DOM.

    Diesen Thread anzeigen
    Rückgängig machen
  8. 5. Feb.

    [2/7]How does one retroactively collect form inputs? From what I can tell, Mixpanel saves all input data from the time of install and uses a heuristic to filter out "sensitive fields such as password or hidden fields". The password leak was caused by a failure in that heuristic.

    Diesen Thread anzeigen
    Rückgängig machen
  9. 5. Feb.

    Mixpanel (an analytics service) was inadvertently collecting user passwords for months. [1/7]Some context: The Autotrack feature, which caused the leaks, allows sites to "retroactively" collect analytics on user form inputs.

    Diesen Thread anzeigen
    Rückgängig machen
  10. hat retweetet
    28. Jan.
    Rückgängig machen
  11. hat retweetet
    5. Jan.

    Hello, Ph.D students! I bring news from professor land. You know how when you’re doing research you constantly feel like you have no clue what you’re supposed to be doing? Turns out that doesn’t go away when you become a professor. We just act all confident when we advise you.

    Diesen Thread anzeigen
    Rückgängig machen
  12. hat retweetet
    31. Dez. 2017
    Antwort an

    The Firefox equivalent: navigate to about:config and change 'signon.autofillForms' to false

    Rückgängig machen
  13. hat retweetet
    31. Dez. 2017

    Here's how to set Chrome's password filler to manual mode:

    Rückgängig machen
  14. 27. Dez. 2017

    New research: Web trackers harvest email addresses by injecting invisible login forms and reading back any auto-filled data. w/ Gunes Acar and

    Rückgängig machen
  15. hat retweetet
    19. Dez. 2017
    Rückgängig machen
  16. hat retweetet
    19. Dez. 2017

    Do research where CS meets consumer protection? Submit a five-pager to ConPro, co-located w/ . Just over a month left:

    Rückgängig machen
  17. hat retweetet
    15. Dez. 2017

    Criteo's workaround for Intelligent Tracking Protection used fingerprinting? "using HTTP Strict Transport Security Protocol, usually used to secure web connections, allowed it to create a user ID without cookies"

    Rückgängig machen
  18. hat retweetet
    1. Dez. 2017

    Expanding Unwanted Software policy to cover Android apps that collect personal user data without consent: 🙌

    Rückgängig machen
  19. hat retweetet
    29. Nov. 2017
    Rückgängig machen
  20. hat retweetet
    20. Nov. 2017
    Rückgängig machen

Das Laden scheint etwas zu dauern.

Twitter ist möglicherweise überlastet oder hat einen vorübergehenden Schlucklauf. Probiere es erneut oder besuche Twitter Status für weitere Informationen.

    Vielleicht gefällt dir auch

    ·