[db-wg] 96.0.0.0/20
- Previous message (by thread): [db-wg] 96.0.0.0/20
- Next message (by thread): [db-wg] 96.0.0.0/20
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Thu Nov 16 18:05:08 CET 2006
Hi Randy I think you need the help of ripe-dbm now. Your route object is maintained by MAINT-RGNET MAINT-RGNET uses only pgp your key-cert object holding your pgp key data is maintained by MAINT-RGNET So you need your old key in order to sign the update to your key-cert object with the new key data. If you no longer have this you will have to ask ripe-dbm to temporarily add an MD5 password to MAINT-RGNET. Then you can authorise your change to the key-cert with the password, then take the password out of the mntner. regards Denis Walker RIPE NCC Randy Bush wrote: >> Stab in the dark, so I could be completely off here, but did you try >> adding a "password: RPSL" to the top of the request? (Look at the >> "RIPE-NCC-RPSL-MNT" object for a possible reason to try that.) >> > > yep. still zero response to email to auto-db > > i have a suspicion it may be due to the database having an outdated > pgp key, and i am signing with a new one (bellovin and austein made > me upgrade a 12 year old one, so don't blame me:-). > > which leaves me with the question of how to change a key-cert: > object without digging up the old key! > > randy > >
- Previous message (by thread): [db-wg] 96.0.0.0/20
- Next message (by thread): [db-wg] 96.0.0.0/20
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]