This is good news, I'm new to this so I read the docs about Digi-ID at (https://www.digi-id.io), it gives a unique public identifier for every domain and I think this is a good idea, but any website can pretend to be another domain while that will expose the public identifier for individuals, and could cause Server to Server impersonation. How does Digi-ID really handle "Domain Spoofing" attacks?
Because DigiByte is being developed and supported by a Core-team and Community (all non-paid volunteers), we can never commit to dates to accomplish future projects. Therefore, please consider future projects to be flexible in time. We have a DigiByte Pipeline instead: DigiByte Pipeline A list of items that we want to do for DigiByte, some with / without bounties etc attached, and others simply as a great way to cut your teeth on DigiByte. Visit DigiByte Pipeline DigiByte Monthly Updates Here you can find what is currently being worked on and what has been accomplished on a month to month basis. Visit DigiByte Monthly Updates
The wallet you are using must show you the domain that you are about to sign to prevent fishing
Fake domain names can be made which look like the legit domain name.
For the phishing attack to work someone needs to 1) go to the wrong domain in first place. This could be easily done through false advertisement 2) ignore the request to check the domain. The wallet app will show the domain of the site you are logging in to. Even if close if you check this against one on the browser and they don't match you have thwarted the attack attempt. Yes it can't prevent phishing attack if people don't do the double check when logging in.
Обсуждают сегодня