Jump to content
bckasman

Patch C - PWM passwords masked, disk activity.

Recommended Posts

Glad to hear you're on top of it Danila. Here's an update: I have a relatively small number of accounts, so I deleted them and started over. Everything works perfectly now (the passwords are not expired, password strength is shown, etc.) except that PWM doesn't start at startup even though the option is checked in settings. Obviously redoing the password database isn't an option for folks with a lot of accounts, but perhaps it helps indicate what's causing the problem.

 

Rich, appreciate your input as always. I didn't send anything as Danila is obviously on top of the issue.

 

BC

 

That is nice that you have a small number of accounts in your pm database. Some of us though use it extensively and have a large amount of passwords in the database. For me, starting new is unacceptable.

 

I just wanted to let you know that this problem must be fixed, telling people to start the db all over is not going to work.

 

IMHO, it appears that somehow in your code you set the "flag" to default to all passwords expire (to force people to change them periodically, which theoretically is a good idea,,,,) but you did not put in a default date to start the countdown from, so it went with all 0's which is where that 1/1/1601 date comes from.

 

So, it would seem that a fix would require 2 things. First, go through each and every password and change the "expired date" to (now + 90 days) to make every one of them be put back into a "good" status.

Then go through and set all of the flags on each password back to "password never expires".

 

You also need to create a settings page for the password expiration. You put this in without a lot of thought going into it.

The user needs to have a "global default" whether that will be on or off. And a way to update all passwords to the default if the user chooses.

The second thing the user needs to set is that if they choose to use this, what the default amount of time will be. You can put in some common choices such as 30,60,90, 180,365 days, but also allow the use to enter a value.

 

Thanks,

 

Jim.

edit: 7 bold portion = Off.

Edited by richbuff

Share this post


Link to post
That is nice that you have a small number of accounts in your pm database. Some of us though use it extensively and have a large amount of passwords in the database. For me, starting new is unacceptable.

 

I just wanted to let you know that this problem must be fixed, telling people to start the db all over is not going to work.

 

IMHO, it appears that somehow in your code you set the "flag" to default to all passwords expire (to force people to change them periodically, which theoretically is a good idea,,,,) but you did not put in a default date to start the countdown from, so it went with all 0's which is where that 1/1/1601 date comes from.

 

So, it would seem that a fix would require 2 things. First, go through each and every password and change the "expired date" to (now + 90 days) to make every one of them be put back into a "good" status.

Then go through and set all of the flags on each password back to "password never expires".

 

You also need to create a settings page for the password expiration. You put this in without a lot of thought going into it.

The user needs to have a "global default" whether that will be on or off. And a way to update all passwords to the default if the user chooses.

The second thing the user needs to set is that if they choose to use this, what the default amount of time will be. You can put in some common choices such as 30,60,90, 180,365 days, but also allow the use to enter a value.

 

Thanks,

 

Jim.

 

 

Jim,

 

There's no need for sarcasm and yelling - your very big and bold "large" to most people would be the same as yelling. I only offered an option for those who could use it and the reported my results. We, in this Forum, are users like you trying to be helpful where we can and offer suggestions if they work for us. Obviously the folks at Kaspersky Lab need to fix their code, which they are doing. Not that it matters much, but I was the one who started this thread. Timing is everything and I must have caught the patch update soon after it's release and noticed the PM issue right away. I, like many, find it odd that this issue did not show up in beta testing, but that sometimes happens. I find it stranger yet that the date that shows is so far in the past. Once PM is fixed, perhaps we can look back and have a little chuckle over the date!

 

By the way, I tried changing the expired date to a date in the future with the idea of going back and checking the never expires box, but, whatever is in the code, it will not accept any changes, except what I've previously reported doing. As I've already said, that's not a good option for folks with a large database, and it certainly doesn't fix the problem. It was an observation, however, that hopefully gave the folks at Kaspersky a better idea of where to look to fix the problem.

 

Hopefully for you and others with a large database, the problem will be fixed soon.

 

BC

 

edit: quoted portion 7 bold = Off.

Edited by richbuff

Share this post


Link to post

KPURE 3 just updated to patch C (few days earlier).

All of my account passwords are now masked (******) and I cannot access them directly.

For example if I want to copy the password for an account from:

Actions->Copy->Password (the item is disabled)

 

Current issue: My Yahoo! password expired, and I have to type my current password then the new. The problem is that the current password is not inserted by the PM and I cannot copy it via the menu listed above (as the item is disabled).

If I choose the "EYE" from BULLETS I am exposed to "*****".

 

Please fix as I am currently locked and I need urgent access to my accounts. If this cannot be fixed in the next few days, I will drop the KPURE license.

 

Thank you!

Edited by vizel

Share this post


Link to post
Hopefully for you and others with a large database, the problem will be fixed soon.

 

BC

 

As my signature states, I'm an "Armchair Geek" with limited Tech Knowledge (Very limited). But I am totally confident that Kaspersky will fix this issue without anybody losing any data entries. The Passwords are still there since we are still able to log into accounts, we just can't see them. As far as time, I trust they are taking the "time" to cross their T's and dot their i's. We are all human and that means we are flawed so we are prone to mistakes now and then. I'll never use anything but Kaspersky because there is no alternative.

Share this post


Link to post

Any word on this? I'm having the same issue. Shows expired 1601, won't let me change expiration, can't update passwords or see them(which means I can't copy and paste either).

 

Have far too many PW's to start over. I've included the screenshot and GSI Report as requested. Hopefully this is resolved soon. Has anyone tried reinstalling without updating to see if that will work in the interim?

post-471267-1382203483_thumb.jpg

GetSystemInfo_GHOSTWALKER_Tob_2013_10_19_10_21_29.zip

Share this post


Link to post

Hi All: This must be a tough problem 'cause it is taking quite a while for the fix. My Pure3 is updating a couple or more times a day but still comes back as 558c and the problem persists. Any news? Will that 558c change when the fix is out? I don't understand much of this stuff and trust Kaspersky but to be fair it seems to be taking too long for a fix. KDM

Share this post


Link to post
Hi All: This must be a tough problem 'cause it is taking quite a while for the fix. My Pure3 is updating a couple or more times a day but still comes back as 558c and the problem persists. Any news? Will that 558c change when the fix is out? I don't understand much of this stuff and trust Kaspersky but to be fair it seems to be taking too long for a fix. KDM

 

Hello Duke One, I am assuming that Kaspersky is being very cautious in their quest to fix this since it involves millions of user's sensitive passwords. I have disabled auto update for now so as not to further complicate a fix but Admin may not advise this. This is just my personal choice.

Share this post


Link to post
Hello Duke One, I am assuming that Kaspersky is being very cautious in their quest to fix this since it involves millions of user's sensitive passwords. I have disabled auto update for now so as not to further complicate a fix but Admin may not advise this. This is just my personal choice.

If I remember correctly (that happens once in a while!) this started with a "large" update that required a reboot. Daily updates cover virus profiles, no? If that is true it might be better to keep the other parts of Pure3 updated. No comment on that detail from Kaspersky? KDM

Share this post


Link to post
Jim,

 

There's no need for sarcasm and yelling - your very big and bold "large" to most people would be the same as yelling. I only offered an option for those who could use it and the reported my results. We, in this Forum, are users like you trying to be helpful where we can and offer suggestions if they work for us. Obviously the folks at Kaspersky Lab need to fix their code, which they are doing. Not that it matters much, but I was the one who started this thread. Timing is everything and I must have caught the patch update soon after it's release and noticed the PM issue right away. I, like many, find it odd that this issue did not show up in beta testing, but that sometimes happens. I find it stranger yet that the date that shows is so far in the past. Once PM is fixed, perhaps we can look back and have a little chuckle over the date!

 

By the way, I tried changing the expired date to a date in the future with the idea of going back and checking the never expires box, but, whatever is in the code, it will not accept any changes, except what I've previously reported doing. As I've already said, that's not a good option for folks with a large database, and it certainly doesn't fix the problem. It was an observation, however, that hopefully gave the folks at Kaspersky a better idea of where to look to fix the problem.

 

Hopefully for you and others with a large database, the problem will be fixed soon.

 

BC

 

BC,

 

Sorry if you felt I was yelling, I was just trying to really emphasize that people with a lot of passwords would not be happy to be told to start over. Yes, I understand for someone with only a few entries, it is no big deal. I do not know your level of involvement with kaz, I just got the impression you were associated with them.

I have seen other situations where a company took the "easy way out" and with your recommendation being an "easy way out" I wanted to chime in to emphasize that it does need to be fixed.

 

You are correct, there is a bug on existing entries where they can not be manually changed. My comments were for you (meaning kaspersky programmers) to change all of those dates by code in an update.

 

If I remember correctly, I believe that my explanation for the date being 1/1/1601 comes from how computers use that date as a starting point. The "current date/time" is actually a number that represents the amount of time that has passed since that starting point. So when they did the update and "turned on" the password expirations, since there was no date on the existing passwords, it defaulted to zero.

 

I hope it is fixed soon.

 

Jim.

 

 

Hi ALL,

 

Thanks for the signal! We will check these problems and will release a fix.

 

Just wondering, will there be a notification of a fix for this issue posted on the forum?
Yes. But in the next week.
Edited by richbuff
You were. But I fixed it. Quotes of important posts were added. Topic is closed for now, for a cooling off period, and so the important content does not get lost in the flood again.

Share this post


Link to post

I updated to the latest C patch in pure 3.0 and now the password manager runs really slow, i click on PWM in pure and it always says start PWM i click start and it takes about 2 minutes before i get type master password window, i enter password than it takes another 2-3 minutes to say PWM is activated like the key in the lock with the green light it's the same when i turn off PWM takes like 2-3 minutes before key removes and green light disappears, it's some kind of bug i imagine in patch C...even after waiting long times for PWM to activate it works flawlessly but its the waiting time thats a bit annoying...operating system is win7 x64 on asus rampage iv extreme motherboard, cpu 3970k, ram corsair gt 16gig 4x4 sticks @ 2133mhz...the only thing i haven't done is re-install pure 3.0 altogether maybe that might fix this issue, maybe someone has a solution to this before i re-install...Thankyou.

Share this post


Link to post
Please submit GetSystemInfo 5 utility report: http://support.kaspersky.com/3632

Please note, that by default the *.zip archive containing the report is saved on the desktop.

 

Thanks for the reply, so i generated a GetSystemInfo log and when i go to sent it i get this error.

 

Fatal error: Allowed memory size of 419430400 bytes exhausted (tried to allocate 24 bytes)

in /data/www/getsysteminfo/www/DEV/includes/functions_parser.php on line 470.

 

I'm using Firefox 24.0 as my browser, would you like me to upload it to this thread i created or other means to customer support...Thanks again.

 

 

Share this post


Link to post

All sorted now, i just went thru my Kaspersky account to submit report...thanks for your help. :ay:

 

Typing error in first post...CPU is a Intel i7 3930k LGA 2011.

Edited by Missing Link

Share this post


Link to post
I updated to the latest C patch in pure 3.0 and now the password manager runs really slow, i click on PWM in pure and it always says start PWM i click start and it takes about 2 minutes before i get type master password window, i enter password than it takes another 2-3 minutes to say PWM is activated like the key in the lock with the green light it's the same when i turn off PWM takes like 2-3 minutes before key removes and green light disappears, it's some kind of bug i imagine in patch C...even after waiting long times for PWM to activate it works flawlessly but its the waiting time thats a bit annoying...operating system is win7 x64 on asus rampage iv extreme motherboard, cpu 3970k, ram corsair gt 16gig 4x4 sticks @ 2133mhz...the only thing i haven't done is re-install pure 3.0 altogether maybe that might fix this issue, maybe someone has a solution to this before i re-install...Thankyou.

 

I got the same behaviour. Once the PWM was unlocked I could add the FF add-on but not the TB one. Before I started I turned the protocolling on. I tried the shortcut Ctrl+Alt+R, which showed up, so I entered some letters of an existing account. FF started and had the key symbol in a green round spot. Moving the mouse over it and trying to open the list failed. I kept pationed and waited until every work was done and it was only then that I could close all the open panels. At the end I could deactivate protocolling, generated the report and hit the send button.

Question: It either sent the 200 MB completely unvisable in the background or it failed. Where could I check?

Some more things, that I should mention:

The shortcut popup worked only once, I tried it several times, nothing happened. Ths add-on for TB could be installed after I finished with the above.

Share this post


Link to post

In my windows 7 computer, all my passwords were marked as expired (01-01-1601) without possibility of copying, seeing or exporting passwords and without possibility of changing the date of expiration. I've lost every password (close to 100) thanks to the software that is for protect passwords. It's possible to see other people with the same problem in this forum. In the same week, my other computer with Windows 8 was upgraded to windows 8.1 (released last week) and Kaspersky Pure stopped working on this new version. None of my two computers are working. I guess a big number of users don't have the information they need to continue with their job. In my opinion, Kaspersky Pure is too unstable and the support is too slow to solve such huge problems.

 

Edit: Merged. And........

 

 

Hi ALL,

 

Thanks for the signal! We will check these problems and will release a fix.

 

Just wondering, will there be a notification of a fix for this issue posted on the forum?
Yes. But in the next week.
Edited by richbuff

Share this post


Link to post

Being without all my application passwords is really getting to be a problem and seeing how this may take awhile, does anyone know how to export the Kaspersky PWM database or some other way to transfer them to another PWM?

Share this post


Link to post
In addition to what I mentioned above, Password Manager no longer starts with system startup. There's also a problem with the passwords. They are learly working, but if I clock on the icon to show the password, it just shows a row of small stars, and I don't see anything that indicates the password strength This sure doesn't look like a fix to me! Has anyone else seen this yet?

 

BC

 

I have exactly the same issue since the update. "New" passwords or identities seem to save correctly, and the password can be viewed. Old ones however are all asterisks, and also the option to copy to the clipboard for previously configured passwords isn't active. They do seem to work though.

Share this post


Link to post

Hey There, I have Kaspersky Pure 3.0 / 13.0.2.558 ©

I did not update Kaspersky Few days ago , but yesterday I ran kaspersky update and it needed to reboot my computer.

But after that I saw my Kaspersky Pure Password Manager in a new style Like as a new version of password manager

but it's really very slow , I can't browsing sites well in all of my browsers . kaspersky pure 3 last update really slowing down all of my computer not only browsers

And since the last update last night I hear my laptop processor fan sound

Please help me and tell me how I can fix this problem or How I can downgrade my password manger :blink:

Share this post


Link to post

I have patch C and a few things seemed to be fixed but now but I just noticed again in password manager that I still get the data sync failed in the lower left of the window.

It shows the user account with a green check mark but below an orange exclamation mark with a sync failed and when I click the "Sync Now" button I get the same thing.

 

I thought they fixed this?

 

PS: Password manager also froze up on me as well. I had to close it with task manager as it would not respond. I hope they fix this soon and not take another 6 months.

 

Edit: I am going to take a wild guess that you are not using Kaspersky Internet Security & Anti-Virus. I think my guess is correct, so I will move this New Topic from the Kaspersky Internet Security & Anti-Virus section of this forum and move it to the PURE section of this forum, and then Merge to the already pre-existing topic, then send you the link to your post. :)

Edited by richbuff

Share this post


Link to post
Please, create a request to tech.support and post here the number.

 

 

Hi Rodion, i did exactly what you have asked...created a GetSystemInfo log sent it to tech support using my Kaspersky account under (My Request Tab) but i haven't received a number, either my log is in a waiting line to be read or something went wrong in the procedure of sending the log, but it did say the log was sent successfully, i have checked my email and the inbox of my Kaspersky account but i haven't been sent any tech support number...Thanks.

Share this post


Link to post

Hello K.L. It is Tuesday in California USA if the fix is not ready how about a bit of news so we know where things stand? I'd bet this is a hard nut to crack and I'm doing OK with the problem but would like to hear about what progress is being made.

Thanks, KDM

 

Edit: Merged. And ran topiccleanmgr.exe. And add quotes of the important posts........

 

 

Hi ALL,

 

Thanks for the signal! We will check these problems and will release a fix.

 

Just wondering, will there be a notification of a fix for this issue posted on the forum?
Yes. But in the next week.
Edited by richbuff

Share this post


Link to post

Hello,

I put Pure update on manual in order to avoid installing the problematic Patch C, as I am a password manager user, but this prevents me from updating databases, thus putting my computer at risk.

I cannot wait much longer with my computer not being fully protected.

Suggestion : since the password manager seems to be a recurring problem maker and considering that my computer protection is my main preoccupation, maybe Kaspersky could provide information on how to completely disable or even remove the password manager from the Pure program.

Any feedback on how to do this will be appreciated.

Edited by Safukeu

Share this post


Link to post

Hello Safukeu, I believe you can set PWM to "Manual Start" within the PWM settings. That way it stays more or less dormant as far as your operating system is concerned. The main culprit with it running is the file stpass.exe continuously writing to file. Mine is on manual start and everything else is running fine. After you set it to manual, log out of PWM then you can either restart or open "Task Manager" and kill the stpass.exe process. Once it is set to manual, stpass.exe will not load until you start PWM. Hope this is part of what you were looking for.

Edited by ENIAC 2

Share this post


Link to post

Hi ALL!

 

We are planning to release a patch "D" tomorrow.

Share this post


Link to post
Guest
This topic is now closed to further replies.

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.