anchor
anchor copied to clipboard
greymass
Can not change nor add extra keys on WAX account.
I got a Ledger Nano S updated to the latest firmware. I'm trying to change the keys as I have the fear that my Ledger seed has been compromised. Of course I have moved everything on a safe location. So I go and log in to wax.bloks.io and select the owner account and then I have to confirm the transaction in my Ledger which happens fine. Note that the message on Ledger is sign transaction at this stage. I go to the section where I change the keys I put the 2 new ones and click confirm. I get the pop up window ( btw I have already change the settings to allow Anchor to sign dangerous transactions) and I'm directed to my ledger to sign the transaction. I click to the right until I get an option that says continue review. I click it and then I get a message in an Anchor popup window asking me to enable contract data on the Ledger device. Something I have already done.
I also tried to add keys/permissions and the same thing is happening.
Please advise!
I hope this is a clear explanation. If needed I can do screenshots.
Thank you
do you need to authorise every new device?
On Sat, Jun 26, 2021, 03:43 DrYunani @.***> wrote:
I got a Ledger Nano S updated to the latest firmware. I'm trying to change the keys as I have the fear that my Ledger seed has been compromised. Of course I have moved everything on a safe location. So I go and log in to wax.bloks.io and select the owner account and then I have to confirm the transaction in my Ledger which happens fine. Note that the message on Ledger is sign transaction at this stage. I go to the section where I change the keys I put the 2 new ones and click confirm. I get the pop up window ( btw I have already change the settings to allow Anchor to sign dangerous transactions) and I'm directed to my ledger to sign the transaction. I click to the right until I get an option that says continue review. I click it and then I get a message in an Anchor popup window asking me to enable contract data on the Ledger device. Something I have already done.
I also tried to add keys/permissions and the same thing is happening.
Please advise!
I hope this is a clear explanation. If needed I can do screenshots.
Thank you
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/1138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASX2FAKB7L7QMGMYY2YGNJLTUWVM3ANCNFSM47LHJPHQ .
We're investigating this now and will hopefully have a fix in the next release (provided we can reproduce and track it down).
Let me know if you want me to do screenshots or a screen recording in case that helps. Thanks
On 1. Jul 2021, at 23:41, Aaron Cox @.***> wrote:
We're investigating this now and will hopefully have a fix in the next release (provided we can reproduce and track it down).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/1138#issuecomment-872568167, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATVSSPB75TQXZAGWNBZE4N3TVTOHFANCNFSM47LHJPHQ.
Screenshots might actually help.
I just went through some tests for an account, using the owner key associated to a Ledger, and attempted to update the keys - all which worked fine. It's possible there's something going wrong in the input steps of that process that I'm just not encountering.
If you want to send them to [email protected] vs posting them here, that's fine as well!
FYI I have sent you the screnshots na d screen recording. I also tried version 1.2.6 still same thing. Also on top when you go to Bloks and try to add a new permission under the advanced section a request it doesn't even come to the Ledger device. To change the keys in the simple section it comes but asks to continue the review instead of signing the transaction. I hope this helps.
Just to follow up on this - I wanted to confirm the emails were received and we have been trying to reproduce and fix this issue.
So far we haven't been able to and are trying to figure out exactly what's different. You mentioned the new 2.0.0 version of the Ledger firmware in your email - which I think might actually be the cause of these problems. The EOS Ledger app itself might have to be updated for this new firmware, and sadly we aren't the developers/maintainers of that app. This means we're going to have to reach out through other channels and try to get the app updated.
I am trying to get a device free'd up right now for testing. Right now all of our devices are on the 1.x firmware and no problems seem to exist there. Once we can get a device available to upgrade to 2.x, we'll do another round of testing and hopefully be able to reproduce the issue.
Thank you for the update. Let me know if there is something else I can do to help. Will be waiting to hear the results after you upgrade to 2.0.0. Thank you
On 14. Jul 2021, at 00:20, Aaron Cox @.***> wrote:
Just to follow up on this - I wanted to confirm the emails were received and we have been trying to reproduce and fix this issue.
So far we haven't been able to and are trying to figure out exactly what's different. You mentioned the new 2.0.0 version of the Ledger firmware in your email - which I think might actually be the cause of these problems. The EOS Ledger app itself might have to be updated for this new firmware, and sadly we aren't the developers/maintainers of that app. This means we're going to have to reach out through other channels and try to get the app updated.
I am trying to get a device free'd up right now for testing. Right now all of our devices are on the 1.x firmware and no problems seem to exist there. Once we can get a device available to upgrade to 2.x, we'll do another round of testing and hopefully be able to reproduce the issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/1138#issuecomment-879444425, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATVSSPDZCPI4JNA75I2M5ELTXS33RANCNFSM47LHJPHQ.
One of our users apparently reached out to the Ledger team and found a temporary solution.
https://forums.eoscommunity.org/t/nano-ledger-s-contract-data-enabled/3918/6
The 1.4.2 EOS App looks to be the source of the issue, and rolling back to 1.4.1 seems to work. I haven't tested this myself, but there's a link in that post to the Ledger subreddit with more discussion on the issue.
Thank you very much for the info will try it and let you know if it worked.
On 14. Jul 2021, at 20:36, Aaron Cox @.***> wrote:
One of our users apparently reached out to the Ledger team and found a temporary solution.
https://forums.eoscommunity.org/t/nano-ledger-s-contract-data-enabled/3918/6 https://forums.eoscommunity.org/t/nano-ledger-s-contract-data-enabled/3918/6 The 1.4.2 EOS App looks to be the source of the issue, and rolling back to 1.4.1 seems to work. I haven't tested this myself, but there's a link in that post to the Ledger subreddit with more discussion on the issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/1138#issuecomment-880121342, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATVSSPH6UEF2R7RIBIEWXNDTXXKMHANCNFSM47LHJPHQ.
@DrYunani @aaroncox Today Ledger Support replied by email saying that version 1.4.3 is already available and that the problem should already be solved.
