retiring gets(3)

[Dier Retlaw Semaj]

In article geoff at utstat.uucp (Geoff Collyer) writes:
>
>The recent exposure of the security bug in the 4BSD fingerd caused by
>use of gets(3) reminded me that gets is a bug waiting to happen and
>should be stamped out.

Would someone please explain me what the problem with gets(3) is,
or point me in appropriate direction of something that would.
I'd be interested in finding out.

Thank you.

-- 

Dier R. Semaj	{ames,cmcl2,rutgers}!rochester!kodak!fedsys!wally!jwr

--