gnuherds-app-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new timestamp data base field for: Lost_Password.php, Person.php, Co


From: Davi Leal
Subject: Re: new timestamp data base field for: Lost_Password.php, Person.php, Company.php & non-profit_Organization.php
Date: Thu, 19 Apr 2007 17:14:36 +0200 (CEST)

Victor Engmark wrote:
> Davi Leal wrote:
> > The field will contain the last time stamp of the lost-password or login
> > forms use, for such entity. What do you think about?
> >
> >             E1_LastTimeStamp  timestamp,
>
> If the table is named something like PasswordRetrieval, yes. It should be
> obvious from the table and column name what it contains.

It is not just for password retrieval, we have to use too for the
register forms, due to they has the same security problem.


What I propose is to add the above new field to the  E1_Entities  data
base table, and use it to save any of the below time stamps:

 1. The last timestamp related to   Lost_Password.php, and

 2. The last timestamp related to   Person.php, Company.php or
    non-profit_Organization.php register forms.

    I propose too this second case (2.) due to the Person.php,
    Company.php & non-profit_Organization.php register forms has too
    the same security problem, due to when a new user try to register
    to the web site, if the email she want to use is already at the
    data base, those forms shows a warning:

      "You can not use it, ... that email is already used
       in the data base ..."


What do you think?

Davi
--

P.S.: You could take a quick look at the  E1_Entities  table,
  Layer-0__Site_entry_point/doc/GNUHerds__SQL_Implementation.psql




reply via email to

[Prev in Thread] Current Thread [Next in Thread]