Hey all,
My webserver went down earlier this week, and I have moved
my mail. I am in the arduous process of getting a new
replacement. I apologize for the delay however, on the
rc.subr colorization project, and hope to have the newest
updates available again soon.
--
Coleman Kane
__
In most implementation I saw it was coupled with a rfid card (short
distance < 1inch (2.5cm))
And for usage at entrance of datacenter -> a network of camera.
Its not spy proof... but good enought for your average lamer.
Fredrik Lindberg wrote:
Alin-Adrian Anton wrote:
In that ca
Alin-Adrian Anton wrote:
In that case, it means the "matching" is a proabilistic
distance-computing algorithm. This sux, for any sort of real remote logins.
Yes. That's probably an accurate description.
I'm by no means an expert in the biometric field, far from it.
But in my most humble o
Fredrik Lindberg wrote:
Alin-Adrian Anton wrote:
Fredrik Lindberg wrote:
But that would sort of defeat the whole purpose of biometric
authentication and you could really just use public keys instead
which would be a lot faster and easier than scanning your finger
at each login. :)
Unles
Bharma Ji <[EMAIL PROTECTED]> wrote:
> Is there any way to determine the physical memory(not the virtual address
> space) being allocated to the kernel at any instant? The overall problem is
> that once I allocate say 512 MB to the kernel (virutal address space)
> through the config file at com
Hi
Is there any way to determine the physical memory(not the virtual address
space) being allocated to the kernel at any instant? The overall problem is
that once I allocate say 512 MB to the kernel (virutal address space)
through the config file at compile time, I want to figure out how much of
t
Hi,
Sorry for replying to an old message, but nobody has
responded to this particular question, so I give it
a try ...
Coleman Kane <[EMAIL PROTECTED]> wrote:
>
> One unfortunate thing about /bin/sh: [from the sh(1) manpage]
>
> Only one of the -e and -n options may be specifie
Alin-Adrian Anton wrote:
Fredrik Lindberg wrote:
But that would sort of defeat the whole purpose of biometric
authentication and you could really just use public keys instead
which would be a lot faster and easier than scanning your finger
at each login. :)
Unless you locally encrypt your
Fredrik Lindberg wrote:
But that would sort of defeat the whole purpose of biometric
authentication and you could really just use public keys instead
which would be a lot faster and easier than scanning your finger
at each login. :)
Unless you locally encrypt your private key with informati
Attila Nagy wrote:
Hello,
On 05/05/06 06:44, Scott Long wrote:
CPU1 is being treated as a hyperthreading core instead of a real core,
and is being disabled per our policy on Intel hyperthreading. By
'disabled' I mean that it is started, but it is being excluded from
scheduling decisions, and
Hello,
On 05/05/06 06:44, Scott Long wrote:
CPU1 is being treated as a hyperthreading core instead of a real core,
and is being disabled per our policy on Intel hyperthreading. By
'disabled' I mean that it is started, but it is being excluded from
scheduling decisions, and thus is only runnin
Alin-Adrian Anton wrote:
Fredrik Lindberg wrote:
>
> The only way as I see it (to even make it possible with UPEKs driver)
> is to have a reader at both the remote machine and the client machine
> and then capture a BioAPI record at the client machine and have the
server verify it. But that
Fredrik Lindberg wrote:
>
> The driver should work fine locally. But using it remote (via ssh etc)
> is probably a no-go because verification of the fingerprint records
are done by UPEKs driver at the hardware level.
>
> The only way as I see it (to even make it possible with UPEKs driver)
> is
Daniel O'Connor wrote:
On Friday 05 May 2006 05:38, Alin-Adrian Anton wrote:
http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader
SSH can do pam authentication.
Not sure the driver will work in FreeBSD..
There is bioapi in ports though.
Oops. looks like ports wins again
14 matches
Mail list logo
