Re: Simple resource protection with public keys

From: Henrick Hellström (henrick.hellstrm_at_telia.com)
Date: 04/28/03 

Date: Mon, 28 Apr 2003 11:11:53 GMT

Tim Goodwin wrote:
> I have devised the following protocol.
>
> The client sends a message comprising (the client's idea of) the
> current time to 1-second resolution, and a signature over that
> timestamp made with the client's private key.
>
> The server verifies the signature, and checks that the timestamp
> is within a small delta of (the server's idea of) the current
> time. If both tests pass, access to the resource is granted.

The server should also record the last time stamp and reject any
requests with time stamps not strictly later than the last time stamp
for that client.

Relevant Pages

  • Re: Concurrency Help
    ... The timestamp column is changed whenever ANY data in the row is ... >> An UPDATE operation with a focused WHERE clause is an atomic operation. ... I want to know if a database, ... >>> 1 would overwrite client 2's changes to the db. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Windows wont Sync to NTP server
    ... Peer Clock Stratum: secondary reference ... Reference Clock Update Time: Mar 31, ... Originate Time Stamp: Mar 31, ... With the 0x8 appended to the end I can see the Windows Client coming ...
    (comp.protocols.time.ntp)
  • Re: WSE 2.0 time fault while authentication.
    ... There are two thing that you can use to avoid the timestamp problems: ... It is usually the time skew between client and server machine. ... Syncing the client and server clocks is an impossibility in my case. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Auto populate a form from an open form
    ... When a client calls, you find the correct client record, and add a new record to ... CallStart should be Indexed, but "Allow Duplicates" should be true. ... Microsoft Access MVP ... so that when the user logs the phone call it is given a time stamp - access ...
    (microsoft.public.access.forms)
  • Re: problems inserting a utf8 timestamp with DBD::Oracle
    ... Don't think so as I'm not using Oracle 9. ... Well I'm not saying it isn't a bug in Oracle but this one is a real problem I cannot easily workaround as really I need a timestamp and a date. ... Client is Oracle 10.2.0 XE ... If you then comment out the 2nd block of code and uncomment the 3rd block of code it works i.e it appears it does not like having a timestamp and a date in the same insert. ...
    (perl.dbi.users)