Please Sign In with Norton Account to Ask a Question or comment in the Community
Envoyé le: 2022-12-13 | 13:35 · 20 Replies · Permalien · Traduction:
Trying to import data from 1 Password. The routine set out in the instructions just does not work. It generates a message "Error on upload. Try again." Attempted to upload then from Chrome. Running the downloaded exe file generates nothing. Very very poor system
Envoyé le: 2022-12-13 | 16:52 · Permalien
Hello SBN01. Are you importing from Chrome via the extension or from 1 Password and importing the .csv file?
https://support.norton.com/sp/en/us/home/current/solutions/v125566479
SA
Envoyé le: 2022-12-14 | 01:36 · Permalien
Since the method of importing the csv from 1Password generated the described error message, I then attempted to import from Chrome via the extension. The second route did not generate the jasn file
Envoyé le: 2022-12-14 | 15:19 · Permalien
Use the portion of the article labeled "Import logins from 1Password ".
SA
Envoyé le: 2022-12-15 | 01:42 · Permalien
As I said before using that method doesnt work!!! I generates the error message I described.
The same error message seems to have been experienced by many people using different import methods reported in this forum. There is no definitive answer on the forum. It seems to be related to formatting issues in the csv file which in turn means that Norton has not updated their import mechanism.
get on it Norton
Envoyé le: 2022-12-15 | 16:29 · Permalien
Please post a screenshot of the error message you are seeing. Here is how: https://community.norton.com/en/forums/how-post-image-forums-0
When you have created the csv file convert it to the following format then attempt to import.
https://support.google.com/merchants/answer/160569?hl=en
SA
Envoyé le: 2022-12-15 | 22:32 · Permalien
CSV file conversion need not be enough. It may also be necessary to edit the file format.
Envoyé le: 2022-12-16 | 02:22 · Permalien
Why should a user have to edit the file format? Thats what I pay Norton to do. So they should provide the neccesary manipulation from the file output from another password manager. i will try your suggestion, reluctantly
Envoyé le: 2022-12-16 | 03:53 · Permalien
I fully understand your frustration. I had to edit over 200 login entries in a CSV file and I was really fed up to do so. However if I didn't want to start inserting logins from Opera into NPM manually, there was no other way.
Just a thought, you can edit a few logins and try importing into NPM to see if it works. If so, you can edit the rest of credentials.
Envoyé le: 2022-12-18 | 10:52 · Permalien
Hi Pegasus
I have not yet tried and having spent a bit more time with NPM I think I will not use it. There are several things I don't like about it. It doesn't fill the CVV on credit cards and does a bad job on addresses too.
Envoyé le: 2022-12-18 | 11:24 · Permalien
Are you guys seeing any different results with Edge? IMA. Saving passwords within a browser is a dangerous scenario. I also use Opera GX as well as Edge on different machines. I personally, NEVER, save logins to the browser for the sake of clipboard data being retrieved by outside factors. I also believe that is the pretext behind Norton not saving the CVV and other information in NPM, as it would be the same as verifying "card in hand" as well as your physical identity, if, that information were ever extracted from a browser. It happens more often that one might believe.
SA
Envoyé le: 2022-12-18 | 11:40 · Permalien
I respectfully disagree, having seen 2FA not protect some of my clients over the years. In every case they were saving and using a browser password manager. Just my side of it having seen the scenario many times over many years. Here is just one other professional opinion on the subject.
https://www.bleepingcomputer.com/news/security/redline-malware-shows-why...
SA
Envoyé le: 2023-01-03 | 12:39 · Permalien
Hello again. Just following up to see if we can assist further.
SA
Envoyé le: 2023-01-03 | 13:57 · Permalien
The article you posted talks about saving passwords in browsers and you say that is the pretext upon which Norton does not save CVVs. The article also goes on to say that the solution to the problem is to save the information in a password manager which properly encrypts the data.
There is no mention of 2FA in the article, which as I said is now required for large or unique purchases using a credit card. Therefore the pretext upon which Norton is operating is erroneous. If a user did not want the password manager to store the CVVs, he/she could simply not enter them. I think its more likely NPM is just a bad password manager based on this and various other aspects of its operation.
Envoyé le: 2023-01-03 | 13:59 · Permalien
If you have any sway with Norton, have them put some resources into turning NPM into a product that is usable. In its current state it is not. It has some nice features, but is far too erratic to be really useful
Envoyé le: 2023-01-04 | 08:07 · Permalien
Being stuck on 2FA appears to be a major part of the ongoing issue with users and NPM. 2FA is useful yet it can be bypassed. Recent announcements from other PWM creators have proven that more than once. The main reason as posted prior, that Norton doesn't save CVV information, seems to be that with that information, anyone obtaining scraped or otherwise info from a PWM will then have the "card in hand" information which in fact is the CVV. Only the card holder should have that information. I've personally NEVER allowed any PWM nor browser to arbitrarily save that information for that reason. Just my broader side of things having been in the business for almost 40 years now.
https://us.norton.com/blog/privacy/what-is-2fa
SA
Envoyé le: 2023-01-04 | 09:36 · Permalien
I'm completely satisfied with that NPM doesn't save CVV and I second @SoulAsylum standpoint in this regard. What bothers me however is that NPM sometimes fails to fill up the card validity and owner name. There is a room for improvement.
This thread is closed from further comment. Please visit the forum to start a new thread.