3 ms·
A better comparison would be the client JavaScript rejecting a four-character password, because it knows the backend policy requires at least eight. Done right
by lxgr 4y ago
A better comparison would be the client JavaScript rejecting a four-character password, because it knows the backend policy requires at least eight.
Done right (without e.g. checking for "key down" events to thwart password managers...), this could could actually improve security somehwat by avoiding whatever the user entered (maybe a low-entropy PIN?) hitting the network or backend, besides providing for a faster error response and thereby nicer UX.
> It’s also not fewer packets
It avoids an entire round trip to the issuer's backend and back, which are often still somewhat expensive and slow, given the legacy systems and connections involved.
- amluto 4y ago> It avoids an entire round trip to the issuer's backend and back, which are often still somewhat expensive and slow, given the legacy systems and connections involved. Not if done both client-side and server-side. Right now, if I swipe my magnetic stripe, then terminal will reject it if the stripe has the magic bit set. If the magic bit is clear, the terminal will (eventually, but usually while the customer waits) send a message to the network saying that the card was present and asking for authorization. The network responds. No additional round trip would be needed for the network to deny authorization if the chip was not used.
- lxgr 4y agoAnd that is exactly what happens :)