News for hackers. Stuff that matters.
Re:Linode hacked, CCs and passwords leaked by treahauet on Monday April 15, 2013 @03:33PM (#5553703)
Either this, or a assignable CVV codes. Something like that would be awesome.
Re:Linode hacked, CCs and passwords leaked by dangrossman on Monday April 15, 2013 @03:44PM (#5553783)
That wouldn't work since CVV codes aren't sent with recurring transactions (they can't, since they cannot be stored).
Re:Linode hacked, CCs and passwords leaked by gcr on Monday April 15, 2013 @05:12PM (#5554385)
Why can't they be stored?

Is it a legal requirement to prevent merchants without the CCV from using the credit card?

...oh wait

Re:Linode hacked, CCs and passwords leaked by duskwuff on Monday April 15, 2013 @09:59PM (#5555716)
Because the CVV is used to indicate the "presence" of the customer at a transaction. CVV1 (which is on the magstripe) is used to indicate "card-present" physical transactions, CVV2 (printed on the back) is used for "customer just typed this in" non-physical transactions.
Re:Linode hacked, CCs and passwords leaked by gcr on Tuesday April 16, 2013 @08:55PM (#5561922)
That makes much more sense. Thank you.
Re:Linode hacked, CCs and passwords leaked by jimktrains2 on Monday April 15, 2013 @04:03PM (#5553914)
__should__ not be stored
Re:Linode hacked, CCs and passwords leaked by treahauet on Monday April 15, 2013 @04:35PM (#5554150)
Good point. Regardless, there should be __something__.