104 karma · joined May 9, 2009
3.0.0.0/15 ap-southeast-1 EC2 (Singapore) 3.8.0.0/14 eu-west-2 EC2 3.16.0.0/14 us-east-2 EC2 3.40.0.0/14 eu-west-1 EC2 3.80.0.0/12 us-east-1 EC2 3.104.0.0/14 ap-southeast-2 EC2 3.112.0.0/14 ap-northeast-1 EC2 3.120.0.0/14 eu-central-1 EC2
U2F requires that the server must know exactly which keyHandles to request, based on the username (and probably password) that is supplied earlier by the user, so that the token can take the keyHandle and derive the key.
In FIDO2 "passwordless" mode, there's no username or other identifier presented, so it's just a generic request for credential from the server -- the authenticator has to independently figure out which key to present based only on the origin/domain, and maybe even present a list of stored keys (probably effectively a list of accounts?) to the user for selection. So it'd need some local/resident storage of various bits like the origin, maybe a user-chosen account name, and the actual credential, since it can no longer rely on the server to do store all these bits.
I think that is not quite the norm, lots of these hosts (and home internet connections) tend to have rather bad reputations, and chasing down the various RBLs can get really old really fast, especially since the most common response is to silently blackhole so you don't get a bounce.
From a Yubico blog post (https://www.yubico.com/2018/05/what-is-fido2/):
> WebAuthn and CTAP2 are both required to deliver the FIDO2 passwordless login experience, but WebAuthn still supports FIDO U2F authenticators, since CTAP1 is also part of the WebAuthn specification.
> Like FIDO U2F, the FIDO2 standard offers the same high level of security, as it is based on public key cryptography. In addition to providing unphishable two-factor authentication, the FIDO2 application on the YubiKey allows for the storage of resident credentials. As the resident credentials can store the username and other data, this allows for truly passwordless authentication. YubiKey 5 Series devices can hold up to 25 resident keys. If RSA keys are used, there is a maximum of three RSA with the rest being ECC.
I wonder what the user experience will be like at 25 resident keys, they mention that the YubiKey Manager (ykman) can set/change FIDO2 PIN and reset FIDO entirely, but nothing about managing individual resident keys/credentials.
It seems like it might be a bit challenging to manage this, especially if end-users accidentally register the authenticator multiple times or run out of the 25 slots for some other reason, and be told that they need to reset the whole authenticator and do recovery for all their sites...
From their API doc: https://core.telegram.org/api/end-to-end/voice-calls#key-ver...
> Party A will generate a shared key with B — or whoever pretends to be B — without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a.
> The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.
> Unlocked phones are still relatively rare in the US so I don't agree with your second point either.
As you point out, where GSM networks are concerned, this observation is mostly specific to the US - swapping phones and swapping SIMs has been a reality in the rest of the world for years.
Instead, the main source of friction is frequency bands. When swapping phones, it's not often an issue when switching between locally distributed phone models, since they are the Asia/international models with more band compatibility. When swapping SIMs domestically, it's not an issue for the same reason. When swapping SIMs internationally, phone service typically works, but if you want high speed data _then_ you check for band compatibility.
I'd say that for most of the world, the reduction in friction is real. It's a pity that the US market is so different.
The cards are hard or impossible to find within the HKIA transit area, so you will want to either pick it from a street retailer in HK, or order from their English webstore - http://www.cugstore.com/hk_en/. Street prices are usually cheaper.
(No affiliation, just a happy customer from a few months back. I got their "Greater China 30 Days Data SIM" because I was spending time in Macau and Hong Kong as well.)
I have a few from Unixstickers though, they're printed properly.
(no affiliation, just a customer)
GIRO authorisation ("Direct Debit Authorisation") until recently was fully paper, often on carbonised forms with manual signature, but some of the banks have started offering electronic authorisation recently.
People here tend to fall into three camps: the cash/NETS (local debit card) folks who queue up at the post office or AXS machines to pay, those who do one-off bill payment on e-banking, and those who use GIRO/credit card. It depends on how comfortable people are with technology and e-banking in particular, as well as how skeptical they are of the billing organisation automatically charging the right amount.
[1] http://www.abs.org.sg/financial_giro.php
[2] http://www.aia.com.sg/en/customer-support/premium-payment-ch...
I'm not sure if you can put your ssh keys on a specific (non-login) keychain.
If you want those, you may want to go to Keychain Access > Preferences > First Aid > uncheck "Keep login keychain unlocked".
But in Singapore, the mother lode is probably Koba Electronics[1] in Chinatown..
[1] http://dangerousprototypes.com/2012/08/06/global-geek-tour-s...
However, I would not immediately characterise the copy as written by a US/UK college grad though - it feels like it is written by someone who learnt English on the mainland.
I don't really know why companies in various parts of East Asia don't hire/outsource to someone who actually is highly fluent in English to write/edit their copy. Sometimes I suspect it is simply due to cost, other times I suspect they just don't realise that their fluency is not quite.. 'international English' level
(No offence to anyone who runs/writes for East Asian company websites.)
From a Singaporean perspective, that's the most bizarre part of mobile service in the US. I need to get an unlimited texting plan so that I don't get billed for people sending me texts? Whoa!
http://www.vatican.va/various/basiliche/index_en.html (English page)
[1] http://www.bloomberg.com/news/2012-10-25/singapore-air-to-en...
Spam remains an issue if for whatever reason you're still using rulesets/blacklists/greylisting and the like, instead of Bayesian filtering.
edit: whoops, 'peeters posted just as I did
Facebook - not everyone has a Facebook account (think parents, young kids), you're not Facebook friends with everyone you know, and you don't _want_ to be Facebook friends with everyone you need to contact. I think they have been trying to change this on Facebook Messenger, but still, you need a Facebook account, and that's a line that many people refuse to cross on principle.
Hangouts - not everyone has Google account, because they use another email provider (Hotmail, Yahoo, ISP), and don't want to get "a Gmail account" just to use it. Granted, this might work great for Android users, but in practice, nobody uses this here (except maybe for multi-party video conferencing). Practically don't see iPhone users on Hangouts either; it is very much associated with Android (and hiding in the background, many people don't even know they're logged in because they don't use it, and nobody uses it to contact them).
iMessage - doesn't work on Android. Yes, there are many iPhones in the world, but you are incredibly selective about who you need to contact if they all have iMessage. But granted, this works quite transparently between iPhones.
Now, iMessage (and Viber) is probably the closest to the 0-step-to-add-contact way of WhatsApp. Because there's no process to do that, there's no contact-request 'approval' required from the other side, there's no friction. You add someone to your phone book, they show up in WhatsApp, you send a message or add them to a group. That's it.
It is a lot easier to teach folks to use WhatsApp just because of this. It's about as complicated to use as your platform's built-in SMS client. It is a huge contrast with the 101 features of WeChat, and to a lesser extent, LINE. WeChat is _huge_ with the PRC community here, but that's about it. Everyone else is on WhatsApp.
Viber is probably the next in line, but due to WhatsApp's network effects, it just didn't take off. Sure, it has internet voice calls, but it's known for being a little flakey on the call quality, and by default its notifications can be a bit annoying. WhatsApp never pops things up unless someone sent you a message.
This current resurgence is probably linked to an English translation being posted on e27 in the past 24 hours, before being subsequently picked up by TRS: http://mirror.e27.co/li-ka-shing-teaches-buy-car-house-5-yea...
Just a note that The Real Singapore is not representative of Singapore's media scene.. while it is not quite an equivalent of The Onion, it is also not the first news source for most locals. I am quite embarrassed to see it linked to on HN.
http://www.inomobile.com.sg/2012/07/ino-cp10/
actual retail price now is SGD 79, which is about USD 65. I'm not sure if I can get these at our 7-Elevens, but I think they have something similar with large keys.
[1] http://www.renesys.com/blog/2012/11/syria-off-the-air.shtml
"The Mine Kafon has just been tested by the Dutch Explosive Ordnance Disposal Unit, which has concluded that it is not suitable for mine clearance (which requires a more systematic approach), but at $50 each could be used as a cheap and safe way to identify dangerous areas that need demining."
Paypal and eBay do this. Gmail filters out any DKIM-fail or SPF-fail mails purporting to be from @paypal.com and sends it to spam, with 100% accuracy. Gmail also puts the little 'key' icon next to the sender name, but that's not really important, the point is that any and all fraudulent emails are filtered out with unerring accuracy.
Thus, we don't need to use PGP or whatever, which needs to be handled at the client level. DKIM + DMARC is already here and working at the server level. You don't need to wait for your favourite email client to adopt DMARC.
Yes, if people send emails without going through that SMTP server etc etc.. that's a problem, but also solvable/solved.