On 2/1/08, Michael wrote:
the minimum value is "longer than your attack will wait" and the max
value is "as long as you are willing to wait". but since you've
decided to store the key with the data, it makes absolutely no
difference. attackers don't have to crack the key when you give it to
them.
> Ok, back to topic. I was thinking about to use a saltfile which consists
your attacker is going to take the time to remove the hard drive
before stealing it? how polite.
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Slow DOWN, please!!! |
| Tony Lindgren | [PATCH 37/90] ARM: OMAP: MPUIO wake updates |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Alexey Dobriyan | Re: [GIT]: Networking |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
