Re: RE: [Assp-user] Whitelist

[Ced P. <cp...@fe...>]

Thanks for this explanation. I just found a javascript timestamp
calculator at http://www.csgnetwork.com/unixds2timecalc.html. By plugging
in a few recent values from my whitelist, I determined that the timestamp
is actually for the time at which the whitelist entry is recorded, so
changing the max whitelist days should, in fact, change this value for all
past entries. Apparently ASSP does not delete an entries with timestamps
later than the current time, so entering a large timestamp value would
make an entry effectively permanent.

The reason I was looking into this was that my whitelist has become
corrupted twice in the last few weeks. Most recently, 75% of the entries
were lost. I thought it might have had something to do with the
timestamps, but that does not appear to be the case. I currently have the
max whitelist days set to 365. Has anyone else had this kind of problem
with the whitelist? If so, and if you've found the cause or a solution,
I'm all ears.

Ced


ass...@li... writes:
>Individual entries will be rotated out ofter 90 days of not being used -
>that is to say if you have not heard from or sent to me in 90 days
>(default), I would be rotated out but if you kept in contact with my
>brother, he will remain on your list provided you speak to each other
>before
>the default time period expires.
>If you wish to make a particular entry permanent (for 30 years or so,
>anyway
>:-), you need to change the time parameter.
>The whitelist is in the form of
>
>  <NAME><HEX02><TIMESTAMP> (without the brackets)
>
>The timestamp is the number of seconds past 1st January, 1970 so if you
>modify the timestamp in any ASCII editor (watch out for MS-DOS/*NIX end of
>line parameters to say (31536000 x 60 ((Seconds in 1 year by 60 Years)))
>about 2 billion then you're good till about 2030AD.
>
>Unix will face its own Y2K crisis in 2033 for reasons that can be found
>elsewhere but for all intents and purposes, this should be good enough for
>the lifetime of ASSP.