found the word privilege written wrong ("priviledge") in several
locations. in gnunet-setup even in an cmdline-argument.i prepared two patches for this. one for the gnunet repo, one for the gnunet-gtk repo gnunet gtk: 0001-fix-typo-in-cmdline-arg-priviledge-privilege.patch gnunet: 0001-docs-fix-typo-priviledge-privilege.patch happy hacking
From ab470c7e2d393118bc19c8bac1166aefcd312a10 Mon Sep 17 00:00:00 2001 From: grindhold <[email protected]> Date: Sat, 21 Sep 2019 13:26:37 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20fix=20typo=20'priviledge'=E2=86=92'priv?= =?UTF-8?q?ilege'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README | 2 +- src/datastore/plugin_datastore_mysql.c | 2 +- src/dns/gnunet-helper-dns.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README b/README index e15cd9c26..e23d006b5 100644 --- a/README +++ b/README @@ -326,7 +326,7 @@ You can avoid running 'make install' as root if you run configure with the "--with-sudo=yes" option and have extensive sudo rights (can run "chmod +s" and "chown" via 'sudo'). If you run 'make install' as a normal user without sudo rights (or the configure option), -certain binaries that require additional priviledges will not be +certain binaries that require additional privileges will not be installed properly (and autonomous NAT traversal, WLAN, DNS/GNS and the VPN will then not work). diff --git a/src/datastore/plugin_datastore_mysql.c b/src/datastore/plugin_datastore_mysql.c index c670a6d99..cc5b558ee 100644 --- a/src/datastore/plugin_datastore_mysql.c +++ b/src/datastore/plugin_datastore_mysql.c @@ -77,7 +77,7 @@ * Thats it. Note that .my.cnf file is a security risk unless its on * a safe partition etc. The $HOME/.my.cnf can of course be a symbolic * link. Even greater security risk can be achieved by setting no - * password for $USER. Luckily $USER has only priviledges to mess + * password for $USER. Luckily $USER has only privileges to mess * up GNUnet's tables, nothing else (unless you give them more, * of course).<p> * diff --git a/src/dns/gnunet-helper-dns.c b/src/dns/gnunet-helper-dns.c index 85c72579d..e837d81c6 100644 --- a/src/dns/gnunet-helper-dns.c +++ b/src/dns/gnunet-helper-dns.c @@ -499,7 +499,7 @@ set_address4(const char *dev, const char *address, const char *mask) /** * Start forwarding to and from the tunnel. This function runs with - * "reduced" priviledges (saved UID is still 0, but effective UID is + * "reduced" privileges (saved UID is still 0, but effective UID is * the real user ID). * * @param fd_tun tunnel FD @@ -728,7 +728,7 @@ PROCESS_BUFFER: * 25-39 failed to drop privs and then failed to undo some changes to routing table * 40 failed to regain privs * 41-55 failed to regain prisv and then failed to undo some changes to routing table - * 254 insufficient priviledges + * 254 insufficient privileges * 255 failed to handle kill signal properly */ int -- 2.23.0
From 89c8e31ec07b5874e76c96ca9a1ec8af55491538 Mon Sep 17 00:00:00 2001 From: grindhold <[email protected]> Date: Sat, 21 Sep 2019 13:29:43 +0200 Subject: [PATCH] =?UTF-8?q?fix=20typo=20in=20cmdline-arg=20'priviledge'?= =?UTF-8?q?=E2=86=92'privilege'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- doc/gnunet-setup.1 | 6 +++--- src/setup/gnunet-setup.c | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/gnunet-setup.1 b/doc/gnunet-setup.1 index 8213c558..5e901ce2 100644 --- a/doc/gnunet-setup.1 +++ b/doc/gnunet-setup.1 @@ -8,7 +8,7 @@ gnunet\-setup \- a gtk interface for configuring GNUnet .PP gnunet\-setup is a gtk+ based GUI for configuring GNUnet. -The first time you run gnunet\-setup, the goal will typically be to configure the peer, that is, the set of processes that always run in the background. Those processes should run as user "gnunet" and thus gnunet\-setup should be run as user "gnunet" for this step. Use the "\-e" option to enable automatic priviledge escalation using gksu (if supported by your system). Alternatively, you can of course run gnunet\-setup from the "gnunet" system user account or even as "root". If you see a tab "General", you did start gnunet\-setup correctly to configure the peer. You should now be able to configure which subsystems of GNUnet you want to enable, which databases to use and what your network configuration looks like. After these steps are complete, you should be able to start your peer using "gnunet\-arm". +The first time you run gnunet\-setup, the goal will typically be to configure the peer, that is, the set of processes that always run in the background. Those processes should run as user "gnunet" and thus gnunet\-setup should be run as user "gnunet" for this step. Use the "\-e" option to enable automatic privilege escalation using gksu (if supported by your system). Alternatively, you can of course run gnunet\-setup from the "gnunet" system user account or even as "root". If you see a tab "General", you did start gnunet\-setup correctly to configure the peer. You should now be able to configure which subsystems of GNUnet you want to enable, which databases to use and what your network configuration looks like. After these steps are complete, you should be able to start your peer using "gnunet\-arm". It is recommended that "/etc/gnunet.conf" should be a world\-readable copy of the peer's GNUnet configuration. Note that GNUnet configuration files (as generated by gnunet\-setup) only contain those values that differ from the defaults. Also note that "gnunet\-arm" will by default look for a configuration in "$HOME/.config/gnunet.conf" (or, "$XDG_CONFIG_DIR/gnunet.conf" if "$XDG_CONFIG_DIR" is set); thus, if your configuration is in "/etc/gnunet.conf", you have to pass "\-c /etc/gnunet.conf" to gnunet\-arm or set "$XDG_CONFIG_DIR" to "/etc/". @@ -16,8 +16,8 @@ It is recommended that "/etc/gnunet.conf" should be a world\-readable copy of th \fB\-c \fIFILENAME\fR, \fB\-\-config=FILENAME\fR load config file (default: ~/.config/gnunet.conf) .TP -\fB\-e, \fB\-\-elevate\-priviledges\fR -Try to elevate priviledges to run gnunet\-setup as user "gnunet". This option is only available if libgksu\-support was found on your system. It is ignored if gnunet\-setup is run as user "root" or "gnunet" already. If "gksu" fails, gnunet\]-setup is run as the current user. +\fB\-e, \fB\-\-elevate\-privileges\fR +Try to elevate privileges to run gnunet\-setup as user "gnunet". This option is only available if libgksu\-support was found on your system. It is ignored if gnunet\-setup is run as user "root" or "gnunet" already. If "gksu" fails, gnunet\]-setup is run as the current user. .TP \fB\-h\fR, \fB\-\-help\fR print help page diff --git a/src/setup/gnunet-setup.c b/src/setup/gnunet-setup.c index 2b95f4d4..77734ecc 100644 --- a/src/setup/gnunet-setup.c +++ b/src/setup/gnunet-setup.c @@ -385,7 +385,7 @@ GNUNET_SETUP_quit_cb (GObject *object, gpointer user_data) #ifndef MINGW /** - * Try elevating user priviledges to run as user 'gnunet' or 'root'. + * Try elevating user privileges to run as user 'gnunet' or 'root'. * * @param username user gnunet-setup should be run as * @return #GNUNET_OK on success @@ -538,7 +538,7 @@ main (int argc, char *const *argv) #ifndef MINGW GNUNET_GETOPT_option_flag ( 'e', - "elevate-priviledges", + "elevate-privileges", gettext_noop ( "run as user 'gnunet', if necessary by executing gksu to elevate rights"), &do_gksu), -- 2.23.0
pEpkey.asc
Description: application/pgp-keys
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
