Password Remembering Plugin

  • Thread starter Thread starter prayag.narula
  • Start date Start date
P

prayag.narula

Hi there,


Hey guys I am trying to develop an Intenet Explorer plugin that would
save passwords and allow me to sign up for a service automatically.


Now I have figured out most of the things. I am using Pavel Zolnikov's

now classic method to develop the plug in using C sharp.


http://www.codeproject.com/csharp/dotnetbandobjects.asp


Now I want to how can I know which page asks for a password. And how do

i fill in the passwords. And also which page requires for sign up and
what all data is to be filled for signing up. Should i use HTTP Request

and HTTP web Request?? Wouldn't it be ..uh.. clumsy ??


How do the browsers do it actually ??
 
Hello (e-mail address removed),

Hey guys I am trying to develop an Intenet Explorer plugin that would
save passwords and allow me to sign up for a service automatically.
Now I have figured out most of the things. I am using Pavel
Zolnikov's
now classic method to develop the plug in using C sharp.
http://www.codeproject.com/csharp/dotnetbandobjects.asp
Now I want to how can I know which page asks for a password.

you need to keep the list of pages where credentials were saved, and check
the new open pages whether it is in that list
And how do i fill in the passwords. And also which page requires for sign up and
what all data is to be filled for signing up. Should i use HTTP
Request
and HTTP web Request?? Wouldn't it be ..uh.. clumsy ??

You need to find the name of control (analyzing the page content) and fill
the user credentials

---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 
Hi,

I have a fingerprint reader on my keyboard that manages passwords for sites and logs my in automatically. It does exactly what
Michael suggested, however I wanted to point out a few more aspects.

In order to successfully submit a login on some websites you'll have to fill in form input elements other than the standard user
name and password fields. In some cases you might even have to select a radio button or click a checkbox. For this reason, you
can't just look for two input text boxes or an input element with a name like "*user*", etc. You'll have to allow the user to
choose which fields are appropriate. Among those fields is the submit button for the form, which might execute JavaScript that is
important for a successful submission, which means you can't just find the first form element and call submit. It will have to be
more dynamic than that.

By analyzing the HMTL on the page and choosing the appropriate input elements that are required to submit a login you'll have to
handle changes to the website by rescanning the page each time to verify that the fields are still there. But there is a potential
problem since a site can be changed entirely or even worse a site can be modified so that the semantics of the existing input
elements are changed or new input elements become required. The latter two cases cannot be automated. You really can't do much
except to remove the site from your internal list or ask the user to update the information when any of the input elements are
missing.

You might even want to store the page to which the user is redirected after a submission and verify that as well. If it is
different you can prompt the user to ask if the credentials were entered successfully or if they need to reconfigure that page. If
successful, store the new "redirected" page reference, otherwise recreate the site in your internal list. (A "Don't ask me again"
option would be necessary as well IMO.)

I had about 20 quick-links at one point and from time to time I noticed that pages would change, of course, and I'd have to reset
the logins for that page. It happened more frequently than I thought it would, but overall it has proven to be quite useful.

GL
 
hi Micheal,

Is thera any other way ro provide username and password? What is I don
not want to save the URL for any reason say security reasons ?

Thanks...

Prayag
 
Hello (e-mail address removed),

Who told u that you need to keep your url in plain text? :)
Just keep the domain name as the key for your pages with url that are encripted
hi Micheal,

Is thera any other way ro provide username and password? What is I don
not want to save the URL for any reason say security reasons ?

Thanks...

Prayag
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 
Hello (e-mail address removed),

Hello (e-mail address removed),

Who told u that you need to keep your url in plain text? :)
Just keep the domain name as the key for your pages that refers to the encripted
url
hi Micheal,

Is thera any other way ro provide username and password? What is I don
not want to save the URL for any reason say security reasons ?

Thanks...

Prayag
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 
:) I somehow saw that coming.....

Basically I din't want to store URLs because I wanted to store the
passwords in a smart card having very limited memory so that its more
secure. And storing all those URLs in smart card would waste precious
memory. Hence wanted some other way..
 
Hello (e-mail address removed),

You should started from that requirement :)

The solution I see is create the hash for each url and keep that hash, not
the url itself
:) I somehow saw that coming.....

Basically I din't want to store URLs because I wanted to store the
passwords in a smart card having very limited memory so that its more
secure. And storing all those URLs in smart card would waste precious
memory. Hence wanted some other way..
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
(e-mail address removed) wrote in @m73g2000cwd.googlegroups.com:
Basically I din't want to store URLs because I wanted to store the
passwords in a smart card having very limited memory so that its more
secure. And storing all those URLs in smart card would waste precious
memory. Hence wanted some other way..

How about hasing the URLs?
 
okay i would be using hashing. It seems a good and viable option..
Thanks a ton...

Also, how exactly do i fill the values in the web page.. I mean can
anyone point me where i shud look for approaching this problem ...
 
Hello (e-mail address removed),

For each hashed url keep the struct with LogonNameControl and PassNameControl
items, and associated user credentials.
Each time user opens that url, just find logon/pass controls and fill them
Also, how exactly do i fill the values in the web page..

---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top