Cursor manipulation

[I. Kobrinsky]

I'm new here.[i]

I started a personal password-program, a trial that includes
username, logincounter and password. So my intention is to
hide pwd while tipping. So I'm thinking about two popular ways
to realize, like using cursor manipulation to backup & delete
letters[***] or otherwise to use getch to read them quetly[ ].

Maybe somebody here knows and will tell me about potentially
dis-/advantages of each method. Meaning especially *intern*
events of program/security aspects. Doesn't mean aspects of its
look. AFAIK getch is almost standard, because a lot of compilers
have it, but generally both methods are non standard. So we get
my first note now:

[i] The compiler I use may vary, flexibility is not the point,
right now I'm testing some different compilers on different
platforms.
My actual question especially belongs to intern events of my
program. Fine. Is there anything that should be considerated
before final decision? Thanks for each useful information to
think about.

[Ioannis Vranos]

I. Kobrinsky wrote:

I'm new here.[i]

I started a personal password-program, a trial that includes
username, logincounter and password. So my intention is to
hide pwd while tipping. So I'm thinking about two popular ways
to realize, like using cursor manipulation to backup & delete
letters[***] or otherwise to use getch to read them quetly[ ].

Maybe somebody here knows and will tell me about potentially
dis-/advantages of each method. Meaning especially *intern*
events of program/security aspects. Doesn't mean aspects of its
look. AFAIK getch is almost standard, because a lot of compilers
have it, but generally both methods are non standard. So we get
my first note now:

[i] The compiler I use may vary, flexibility is not the point,
right now I'm testing some different compilers on different
platforms.
My actual question especially belongs to intern events of my
program. Fine. Is there anything that should be considerated
before final decision? Thanks for each useful information to
think about.

I am not sure what you mean by cursor manipulation, however using
getch() and couting an * for each character entered, should work.
There should be no additional security aspect than usual input using cin.
Unless the vendor's library is broken or something.


--
Ioannis Vranos

http://www23.brinkster.com/noicys

[I. Kobrinsky]

[Question: between cursor manipulation or getch()]

Ioannis Vranos:

I am not sure what you mean by cursor manipulation, [...]
At last I found some information about cursor manipulation
suitable for invisible pwd-input at internet. Actually I'm
going to learn and make trys to realize different methods.
I'm looking forward how its going on. To get a short overview
what I meant about, you may have a look at following page for
example:
http://ou800doc.caldera.com/en/SDK_c...FieldOpts.html
however using getch() and couting an * for each character
entered, should work.
There should be no additional security aspect than usual input
using cin. Unless the vendor's library is broken or something.

Valuable to know. Well, I'll take your information into my
consideration. Thanks very much for your help & 've a nice X-mas.

[Jack Klein]

On 22 Dec 2004 01:58:06 -0800, "I. Kobrinsky" <Iv************@gmx.net>
wrote in comp.lang.c++:

I'm new here.[i]

I started a personal password-program, a trial that includes
username, logincounter and password. So my intention is to
hide pwd while tipping. So I'm thinking about two popular ways
to realize, like using cursor manipulation to backup & delete
letters[***] or otherwise to use getch to read them quetly[ ].
All input and output in the C++ language is defined in terms of
hardware independent streams, either C++ iostreams or C FILE *
streams. There is no requirement or guarantee provided by the
language that any stream is connected to an interactive device or a
video display. There is no getch() function, nor any cursor control
in the C++ language.
Maybe somebody here knows and will tell me about potentially
dis-/advantages of each method. Meaning especially *intern*
events of program/security aspects. Doesn't mean aspects of its
look. AFAIK getch is almost standard, because a lot of compilers
have it, but generally both methods are non standard. So we get
my first note now:
Your questions about security are something else that is not addressed
by the language. And the fact that you happen to think that something
is "almost standard" does not make it topical here. It is not part of
the language, so it is off-topic.
[i] The compiler I use may vary, flexibility is not the point,
right now I'm testing some different compilers on different
platforms.
My actual question especially belongs to intern events of my
program. Fine. Is there anything that should be considerated
before final decision? Thanks for each useful information to
think about.

From a language point of view, there is nothing at all that can be
considered here when selecting between different non-standard and
platform specific extensions.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

[Jack Klein]

On Wed, 22 Dec 2004 13:34:09 +0200, Ioannis Vranos
<iv*@remove.this.grad.com> wrote in comp.lang.c++:

I. Kobrinsky wrote:

I'm new here.[i]

I started a personal password-program, a trial that includes
username, logincounter and password. So my intention is to
hide pwd while tipping. So I'm thinking about two popular ways
to realize, like using cursor manipulation to backup & delete
letters[***] or otherwise to use getch to read them quetly[ ].

Maybe somebody here knows and will tell me about potentially
dis-/advantages of each method. Meaning especially *intern*
events of program/security aspects. Doesn't mean aspects of its
look. AFAIK getch is almost standard, because a lot of compilers
have it, but generally both methods are non standard. So we get
my first note now:

[i] The compiler I use may vary, flexibility is not the point,
right now I'm testing some different compilers on different
platforms.
My actual question especially belongs to intern events of my
program. Fine. Is there anything that should be considerated
before final decision? Thanks for each useful information to
think about.

I am not sure what you mean by cursor manipulation, however using
getch() and couting an * for each character entered, should work.

And what exactly does "getch()" do? Where is it defined by the C++
standard? What if some particular function by that name calls
abort()?
There should be no additional security aspect than usual input using cin.
Unless the vendor's library is broken or something.

Please stop providing off-topic answers to off-topic questions.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

[I. Kobrinsky]

-> Jack Klein!

On 22 Dec 2004 01:58:06 -0800, "I. Kobrinsky" <Iv************@gmx.net> wrote in comp.lang.c++:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
Mr. Klein, Short Your Introduction roman! Quickly!
Do I have to print usenet-netiquette at Your brow??
How long are Jack Klein member of this Newsgroup?
Cant exist! Until now nobody else made sure to get
rebuke you and get linked up to newusers/netiquette??
Your questions about security are something else that
is not addressed
Shut down! Of course security is a very important aspect of
any language.You are not a well developer it seems, otherwise
you never would speak such words. Jack, where to hell have u
lived until now? Get up from your zweet Microsoft Dornröschen
sleep and take a watch at reality!

Nobody, not any developer at thoose days should fuck of security
aspects. Its NOT just a part of later patches & updates. Make
programs going work right, in other words make them secure is
*the* *basicly* question of _any_ development.
[oh my dear... this boy stucked up ~1900.]
--

Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

^^^^^^^^^^^^^^^^^^^What the HELL is ....!??????!^^^^^^^^^^^^^

Can't believe! Its toooo much!! Get short, babe!
Every reply you post, you active stealing OUR space at server!
Some case of Killfile it seems...

[Default User]

I. Kobrinsky wrote:

Can't believe! Its toooo much!! Get short, babe!
Every reply you post, you active stealing OUR space at server!
Some case of Killfile it seems...

I'll be happy to get our newsfeed up so I can killfile this twit.
I wish grouple allowed that.

Brian

[I. Kobrinsky]

Jack Klein:

On Wed, 22 Dec 2004 13:34:09 +0200, Ioannis Vranos
<iv*@remove.this.grad.com> wrote in comp.lang.c++:
-> Hey, Jack, look my last post, its not needed in this Newsgroup!

[help from Ioannis] Please stop providing off-topic answers to off-topic questions.
Right, *my* mistake. Sry, was not my intention.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

Short it up, trough the half!

[I. Kobrinsky]

Default User wrote:

I. Kobrinsky wrote:

Can't believe! Its toooo much!! Get short, babe!
Every reply you post, you active stealing OUR space at server!
Some case of Killfile it seems...

I'll be happy to get our newsfeed up so I can killfile this twit.
I wish grouple allowed that.

Good Luck.

Adios!

[Ioannis Vranos]

I. Kobrinsky wrote:

[oh my dear... this boy stucked up ~1900.]

Strictly speaking, getch() is a system extension and thus off topic in
here. Thus Jack is right, but still strict on this matter (since it is a
commonly used extension).

But he is not wrong when he says that it is off topic.


--
Ioannis Vranos

http://www23.brinkster.com/noicys