Hacker Newsnew | past | comments | ask | show | jobs | submit | m-s's commentslogin

Apple uses certificate pinning for some of its domains, which doesn't play nicely with corporate firewalls.

https://support.apple.com/en-us/HT210060


Either a company block traffic or allows it.

Inconspicuously inspecting traffic to spy on people, even employees, is just bad.

I work at a company that once turned it on for GitHub.com.

All builds that pulled stuff from GitHub started to fail because all those Docker containers don't have the company's root CA trusted.


Getting refunds for App Store/in-app purchases has been a breeze for me though.


How would you “steal” money from a contactless card or a phone?


1) Gain access to something like a Stripe Terminal (https://stripe.com/gb/terminal) You should probably avoid using your real identity here.

2) Type in a charge like $50

3) Discretely wave the device at your targets wallet

4) Repeat steps 2-3 as much as possible in a short amount of time.

5) Hope you can withdraw the funds before anyone notices.

I don't think this is a wildly plausible attack and also at least here in the UK your targets card issuer takes 100% liability for fraudulent charges.


This attack (and some variants of it, e.g. fooling the proximity detection or man in the middle) work because the acknowledgement action that the user does is simply having the device nearby. This seems like a poor choice of acknowledgement action for something that transfers money. Payment devices should probably have a physical or soft button that you have to press to acknowledge payment.


Strong disagree. The usability hit is not worth the added security. Having a cutoff for PIN entry requirement and the card issuer taking responsibility for fraud means customers are quite safe (as long as they look at their charges).


Work could be done to make it more usable. With a phone, it could be a button you could press just by holding it. With a smart watch, it could be hooked into any kind of bluetooth sensor. The point is that in normal society, you don't have that much control over who and what gets into proximity with you, and having a system where anything that does get into proximity can take money from you without you even acknowledging that in any way is just a bad way of doing things.


You could do something like "you need to be physically holding the card with your hand", which would complete some circuit. I can't think of many cases where that wouldn't work, except perhaps people who don't take their cards out of their wallets(?).


> 1) Gain access to something like a Stripe Terminal (https://stripe.com/gb/terminal)

Getting a payments terminal is not easy, this would requires ID verification and working business bank account (acquirer), this terminals are highly regulated. Someone doing this can get caught easily by just a couple of customers reporting the fraudulent transactions. This is very small risk and is rarely seen.


> 3) Discretely wave the device at your targets wallet

Phone payments generally require the phone to be unlocked.

Also, it's a credit card transaction: the user will complain later, attacker will get into legal trouble, and user will be refunded fully.


Most new wallets ac as faraday cages.


For example: NFC Proxy?


Yes, you can. But only drinks with up to 4.7% abv


It's fine to present a pdf, as long as it's legible and the code can be scanned.

> Het E-ticket dat wordt geladen op een mobiele telefoon, tablet of laptop is alleen geldig als vervoerbewijs als het duidelijk leesbaar weergegeven kan worden op de mobiele telefoon, tablet of laptop.

https://www.ns.nl/binaries/_ht_1553092893605/content/assets/...


Yeah I’ve shown PDFs before, and as long as the QR code is scannable the NS conductor doesn’t care.


Literally on the PDF ticket it says it is only valid when printed out in full or when loaded in the app that can only be gotten legally through google or apple.


I have my own domain and run a Cloudflare Workers endpoint that updates a DNS record. It’s quite simple to run one’s own dDNS service.


The pasted text already includes the GTUBE string [1], which is used to test some spam filters.

[1] https://en.wikipedia.org/wiki/GTUBE


You can still click through the phishing warning


You need an iPhone to link your phone number though.


Can’t you mix Apple account with phone numbers if everyone is using iMessage? And if everyone isn’t on iMessage it would defeat the purpose and might as well use an android, no?


You don’t need to link to a phone number for blue bubbles


“willingly” is a bit of a stretch


It depends. I understand that ad networks for example take identifying data (such as IP addresses) without consent. But if I sign up to Facebook and I put there my name and my face, it's because I want to. No one has put a gun to my head. And I don't see that it matters whether that data is in a hard disk in the US or the EU. These regulations seem a power move more than anything else.


The proof of a problem isn't "someone put a gun to my head" - its a meaningful part of our society put behind a rich man's walled garden because only he had enough money to bribe every telecom and buy every competing platform.


Every competing platform? I can think of a few alternatives, starting with this one we are on right now. But some people are still choosing Facebook, and they are choosing it willingly, happy they do not have to pay for it with anything more than some targeted ads...


This is not a competing platform by any stretch of the imagination.


If I send a US citizen a letter, can I expect that it will not be (legally) intercepted and read by anyone else (except under a specific warrant)?

If I send a US citizen a private Facebook message, is it not normal to expect the same?


> But if I sign up to Facebook and I put there my name and my face, it's because I want to

Facebook wouldn't have all its negativity around privacy if they only captured & used data that the user explicitly entered. The problem is that Facebook collects much more data that what you knowingly & willingly give it.


You might have uploaded your name and face willingly to Facebook in order to set up your profile, but without proper safeguards and legislation, the data might be used to train an AI model to use your face to identify your relations with other user using photos, which they also willingly upload, to power features such as people you might know and of course, advertising. The data might also be sold or transferred to third-parities like Cambridge Analytica for political advertising or government agencies for "national security" -- all without your explicit consent.

It is true that it does not matter if a piece of data is stored in either side of the Atlantic, but this is not a engineering problem about data locality and latency. As someone who spent months working on a global distributed GDPR-compliance identity store, my life will be much easier if the problem can simply be solved by paying a slightly higher inter-region data transfer fee.

Unfortunately, US and EU here are not referring to cloud regions, but as jurisdictions because different laws on data protection apply. None of us likes this kind of complexity, but "power move" would be an overly-simplified abstraction of this problem.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: