Timestamps like last_modified_gmt and last_touch are off by -3 hours. I actually first noticed this when tinkering with the lastpass-python library so I think it is actually the lastpass server doing this. But I cannot imagine by what logic this is happening. I can't find this documented anywhere. I don't want to just adjust it by 3 hours without understanding why in case there is something else going on.
If I save a password at 12:00 PST, it comes back as 9:00 PST. This happens whether update the password in the CLI or the lastpass browser extension. The browser extension shows the time correctly so some kind of deliberate conversion seems to be happening but I cannot imagine what. If it was off by 8 hours or 5 hours then I would assume it had something to do with storing it timezone unaware like how windows stores system time. But 3 hours is kind of strange.
Timestamps like last_modified_gmt and last_touch are off by -3 hours. I actually first noticed this when tinkering with the lastpass-python library so I think it is actually the lastpass server doing this. But I cannot imagine by what logic this is happening. I can't find this documented anywhere. I don't want to just adjust it by 3 hours without understanding why in case there is something else going on.
If I save a password at 12:00 PST, it comes back as 9:00 PST. This happens whether update the password in the CLI or the lastpass browser extension. The browser extension shows the time correctly so some kind of deliberate conversion seems to be happening but I cannot imagine what. If it was off by 8 hours or 5 hours then I would assume it had something to do with storing it timezone unaware like how windows stores system time. But 3 hours is kind of strange.