Only XRP Private Keys That Used Software From Before August 2015 Are Vulnerable

[Guest]

"According to Ripple, deterministic nonce generation has also been part of their software since August 2015. This feature also makes addresses that interacted with the blockchain employing newer software libraries safe from this vulnerability". Need someone to translate the latter part...

Does that mean, if you have an old wallet from pre 2015, the old wallet is safe as long as you have sent some Xrp from it to another newer wallet/address that has been created after 2015??

Edited January 20, 2019 by Guest

[Pablo]

This has already been discussed on another thread here. Hope you have access:

 

[Vitamin]

Hi first post.. fear got me here  I cant post in other thread new account. Do you know if ripplerm clients vulnerable. I have no knowledge of code. Im assuming it is, but dont have a clue how to solve. Generated new account, sent funds from old wallet to new. But I think I misunderstood the problem... Its the sending of funds using old library that exposes the secret that is used to sign the transactions? So my secret can be derived from transaction data? What should I do? Send funds to online storage like bit-stamp? Is that the lesser evil? Any help appreciated. https://github.com/ripplerm/ripple-wallet

{
  "name": "ripple-wallet",
  "version": "1.2.4",
  "license": "MIT",  
  "description": "A single page Angularjs app for interacting with Ripple networks.",
  "dependencies": {
    "ripplelib": "^1.2.2",
    "angularjs": "^1.4.4",
    "angular-ui-bootstrap": "0.14.3",
    "highcharts": "^4.1.10",
    "jsonformatter": "^0.6.0",
    "ngstorage": "^0.3.11",
    "file-saver": "^1.3.3",
    "angular-qrcode": "^6.2.1"
  },
  "repository": {
    "type": "git",
    "url": "git://github.com/ripplerm/ripple-wallet.git"
  },
  "readmeFilename": "README.md"
}

 

Edited January 21, 2019 by Vitamin
spelling