Loading ...
Sorry, an error occurred while loading the content.
 

Re: [tracker2] Re: Authentication scheme

Expand Messages
  • Scott Miller
    That s right. I ve got to decide whether it s worth the risk of writing to flash when the user s trying to reset the device because something s presumably
    Message 1 of 22 , Jun 2, 2009
      That's right. I've got to decide whether it's worth the risk of writing
      to flash when the user's trying to reset the device because something's
      presumably wrong with it. For now, it just doesn't update the sequence
      number on reset.

      Scott

      Manfred wrote:
      >
      >
      >
      > Hi Scott!
      >
      > Just to understand this statement:
      >
      > Is that the reason that after a remote reset command you must use the
      > same secret code again for the first command after the reset command?
      >
      > Not having a problem with that - just noticed this after the last remote
      > reset.
      >
      > 73 de Manfred, OE7AAI
      >
      > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
      > Scott Miller <scott@...> wrote:
      > >
      > > It gets stored in flash as soon as the command finishes executing. This
      > > is something to keep in mind if you're doing a reset - it'll never have
      > > a chance to write the updated sequence. I may have to fix that.
      > >
      > > That also means that commands like INFO will generate a flash
      > > erase/write when they wouldn't ordinarily, when run remotely.
      > >
      > > Scott
      > >
      > > J. Lance Cotton wrote:
      > > >
      > > >
      > > > Scott,
      > > >
      > > > How does this work w.r.t. power-cycling of the T2? Is the "next code"
      > > > stored in flash or RAM? What happens if the power cycles or the
      > > > processor resets?
      > > >
      > > > -Lance KJ5O
      > >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.