View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005080 | GNUnet | GNS | public | 2017-06-12 16:00 | 2018-06-07 22:40 |
| Reporter | lynX | Assigned To | schanzen | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | Git master | ||||
| Fixed in Version | 0.11.0pre66 | ||||
| Summary | 0005080: gnunet-gns-import.sh fails to generate gns-master ego | ||||
| Description | Jun 11 15:37:54-140798 gns-10934 INFO No ego configured for `gns-master` This log message is strange since I probably ran gnunet-gns-import.sh before allocating places and hosts with gnunet-social. Maybe it's due to some changes in the code? Rerunning the script unfortunately does not fix it: % gnunet-gns-import.sh Private zone link exists, skipping Shorten zone link exists, skipping A PKEY record exists already under `pin', no other records can be added. I doubt this is useful for end users. GNS should just work out of the box. The existence of a shell script that needs to be run is already beyond user expectation. Maybe it would be enough to add a hint on what to do. Something like "If this is not what you want, try to remove the .local/<whatever>/<obscure>/<path> file and run this script again." Or, even better, simply offer a gnunet-gns-import.sh -C option as in clean-out or something like that. Or can we make this script intelligent enough that it will always create a sane state - removing broken zones as needed? Or do we plan to have end users that actually intentionally want broken GNS? | ||||
| Additional Information | I tried to manually clean out GNS and restart from zero, but: % gnunet-identity -d gnunet - NC9WM9J6Z4FATEF6P8Q8HHSY4SMGYSWSF68FFKC6PHE3XTP93SF0 sks-zone - XFZ5CJ6ZDDZWF26BE4HNVGGMBETD33YX29CWYMRN6J5AMG4G3GH0 short-zone - 9TMFG0RWE76848T555HP4F7PDN8JJKJM3WQP8QPV1WR2K3V6YG90 private-zone - M6PV0YCTGT2MBXDK41ZYJPNGSWHSFJNK9DQS63FFEKHD5ENQS3X0 master-zone - GKGQDAJSYY796Y9W6K4TFFE0GS9MBZ55WA2H0GGBFFGYT49HN82G % gnunet-identity -D master-zone % gnunet-identity -D private-zone % gnunet-identity -D short-zone % gnunet-identity -D sks-zone % gnunet-identity -D gnunet % gnunet-identity -d % make gnsinit gnunet-gns-import.sh Could not set ego to `master-zone' for subsystem `gns-master', ego not known Could not set ego to `master-zone' for subsystem `namestore', ego not known Could not set ego to `master-zone' for subsystem `gns-proxy', ego not known Could not set ego to `master-zone' for subsystem `gns-intercept', ego not known Ego `master-zone' not known to identity service Ego `master-zone' not known to identity service Ego `master-zone' not known to identity service Ego `master-zone' not known to identity service Ego `master-zone' not known to identity service Ego `master-zone' not known to identity service Makefile:168: recipe for target 'gnsinit' failed make: *** [gnsinit] Error 255 Does this mean I also need to remove namestore? | ||||
| Tags | No tags attached. | ||||
|
|
Reminder sent to: Christian Grothoff |
|
|
lynX: I just don't know what is wrong with your system. I can run the script, and it works just fine for me. I can run it twice, and I get some warnings (about operations failing because they were already done before), but IMO that's OK. Yes, things should ideally work 'out of the box', but this logic needs to be run per-user (not per system), and right now we don't have a GUI for it _and_ in theory other configurations might be liked by some users as well. In the 'long' term, my thinking right now is to drop the SKS feature (!) from FS, and maybe also the private zone. Then, we'd want the '.gnu' zone (master zone) to be configurable (pick your own TLD!), and once we make that possible in the UI, we can probably eliminate gnunet-gns-import.sh wholesale: the binding of 'master-zone' to 'gns-master' is then replaced by the TLD-name to zone-key/identity binding in the UI, and most of the rest is gone. We might still want some semi-automatic way to add some FCFS/PIN-zones, but that's not required to get things running, and could be packaged with the GUI and/or gnunet-namestore. WDYT? |
|
|
So... this is done already, right? |
|
|
GNS no longer requires execution of this script. |
|
|
Yes, this script should be dead now, we no longer have a master ego concept. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-06-12 16:00 | lynX | New Issue | |
| 2017-10-27 16:51 | lynX | Note Added: 0012517 | |
| 2017-10-28 19:43 | Christian Grothoff | Note Added: 0012520 | |
| 2018-06-07 22:38 | schanzen | Note Added: 0013015 | |
| 2018-06-07 22:39 | schanzen | Assigned To | => schanzen |
| 2018-06-07 22:39 | schanzen | Status | new => resolved |
| 2018-06-07 22:39 | schanzen | Resolution | open => fixed |
| 2018-06-07 22:39 | schanzen | Fixed in Version | => 0.11.0pre66 |
| 2018-06-07 22:39 | schanzen | Note Added: 0013016 | |
| 2018-06-07 22:40 | Christian Grothoff | Status | resolved => closed |
| 2018-06-07 22:40 | Christian Grothoff | Resolution | fixed => no change required |
| 2018-06-07 22:40 | Christian Grothoff | Note Added: 0013017 | |
| 2018-06-07 22:40 | Christian Grothoff | Product Version | => Git master |
