3 ms·
> Username and password doesn’t inherently have an HMAC+timestamp, so it has to be kept alongside payments. I don't follow your logic here. A userdb record cou
by mindslight 6y ago
> Username and password doesn’t inherently have an HMAC+timestamp, so it has to be kept alongside payments.
I don't follow your logic here. A userdb record could simply consist of user+pass, service level, static public IP, and an expiration date - essentially the same information that a certificate would carry.
The existence of a user record is certainly more legible to the legal system, and might help support a court order to actively surveil that "user's" activity. But from a technical perspective of what information can be gleaned here, they're the same.
- lstamour 6y agoI don’t think we’re disagreeing? :) An expiration date and username is a type of payment record?
- mindslight 6y agoI was referring to a payment record as something that would be useful to follow a trail, such as a cc auth# or transaction IP address.