1Password Chome Extension creates passwords with modified date of 1.1.1970

Manaburner

Hi guys,



I'm using the 1Password Chrome extension in Windows a lot. When I generate a new password, those passwords have a modified date of "01.01.1970, 01:00".



Does anyone else have this problem?



Regards,

Michael

DBrown

I got a different (but equally inaccurate) modified date on a Strong Password generated from the 1Password for Windows extension for Chrome:



[indent][img]http://content.screencast.com/users/DMBrown/folders/Jing/media/328ed8cb-6f63-48cc-add3-08dc5dc95b84/00000156.png[/img]

[/indent]

The problem doesn't occur with a Strong Password generated from the 1Password for Mac extension for Chrome:



[indent][img]http://content.screencast.com/users/DMBrown/folders/Jing/media/bbb23d96-7bcf-4b59-a8a6-2c46ff67a5aa/00000157.png[/img]

[/indent]

I'll mention it to the developers.



Thanks for bringing it to our attention, Michael!

Manaburner

[quote name='DBrown' timestamp='1295460728' post='19216']

Thanks for bringing it to our attention, Michael!

[/quote]



You're very welcome.



Regards,

Michael

jpgoldberg

[quote name='DBrown' timestamp='1295460728' post='19216']

I got a different (but equally inaccurate) modified date on a Strong Password generated from the 1Password for Windows extension for Chrome:

[/quote]



I think that this is the same time if the two of you are five timezones apart.



1970-01-01:00:00:00 GMT has special meaning in the Unix world as the beginning of the universe. It would seem that the tools within Google Chrome can coordinate better with the clock on Unix systems (such as Mac OS X) than on Windows. This gives us a very big hint at where to look for this bug.



Cheers,



-j

Stefan von Dutch

Fixed in 1.0.3.163