home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!news.iastate.edu!vincent2.iastate.edu!viking
- From: viking@iastate.edu (Dan Sorenson)
- Subject: Re: Character supression/FoxPro 2.0
- Message-ID: <viking.722374379@vincent2.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames IA
- References: <4f28_im00VQj48ZPJU@andrew.cmu.edu> <By11z4.Fou@news.cso.uiuc.edu>
- Date: Sat, 21 Nov 1992 19:32:59 GMT
- Lines: 15
-
- In <By11z4.Fou@news.cso.uiuc.edu> jcole@osiris.cso.uiuc.edu (Joan Cole) writes:
-
- >The way I always do the get on passwords is @ X,Y GET passwdvar COLOR N/N
- >Black on black is invisible (although not secure from print-screen)
-
- This is probably fine for 99% of the needs one would have. A
- more secure method would be to clear the keyboard buffer, ask for a
- password, use a getkey() to read keypresses and append them to a memvar.
- If the getkey() shows CHR(13), validate the password or start the routine
- over. CHR(13) as the first keypress returns to calling procedure.
-
- < Dan Sorenson, DoD #1066 z1dan@exnet.iastate.edu viking@iastate.edu >
- < ISU only censors what I read, not what I say. Don't blame them. >
- < "This isn't an answer, it's a pagan dance around a midnight fire >
- < written in intellectual runes." -- Rich Young >
-