Lines Matching refs:t

70 	and password cracking, i haven't really bothered yet to speed up
123 	crypt function and i didn't feel like ripping it out and measuring
165 	table sizes are unclear, but they don't look very small
173 man pages either didn't exist or dumped core.  i had heard of kerberos,
178 (i.e. the author didn't sit down and think before coding),
191 by the larger table size.  in his case he didn't realize you don't need to keep
197 to crypt(3) in his tables - i didn't check.
211 of what i didn't want to do; all their endedness-specific ``optimizations``
218 1) i assume everything is byte addressable, although i don't actually
277 if you don't have 4 register variables get a new machine.
286 	- greater than 127 in value (can't use movq or byte immediate on CISC)
357 	m yourself, you will get a 768bit key - but then it won't
364 	you really shouldn't use the 768bit format directly;  i should