network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Jan 18 at 1:54 | |
| stats | profile views | 1 |
|
Jan 17 |
comment |
Check for database tampering The goal is to be alerted if any data has been altered from the original. Also to make it (virtually) impossible to create a hash with malicious data |
|
Jan 17 |
asked | Check for database tampering |
|
Nov 17 |
asked | HTTP over GPRS - is it secure? |
|
Nov 17 |
awarded | Scholar |
|
Nov 17 |
accepted | Security concerns with pre-pay system |
|
Oct 26 |
comment |
Security concerns with pre-pay system yes, the codes are hashed and salted, in practice. |
|
Oct 26 |
comment |
Security concerns with pre-pay system Wow, great comments thx. Initially the pre-pay system will be site specific, codes can't shared across sites. Franchise or multiple sites will require more thought I think. The code is loaded into an app and as a customer purchases product it is deducted from the total. |
|
Oct 26 |
awarded | Supporter |
|
Oct 26 |
comment |
Security concerns with pre-pay system Yes, the codes are retailer specific. I have another table that tabulates all transactions for each code. Thanks for your comments. |
|
Oct 26 |
awarded | Student |
|
Oct 26 |
asked | Security concerns with pre-pay system |
