1. 21 Jan, 2015 2 commits
  2. 08 Jan, 2015 1 commit
  3. 18 Dec, 2014 3 commits
  4. 15 Dec, 2014 1 commit
    • Jiří Klimeš's avatar
      libnm-core: mute coverity for RESOURCE_LEAK (CWE-772) in g_return_val_if_fail() · afb0e2c5
      Jiří Klimeš authored
      Error: RESOURCE_LEAK (CWE-772): [#def10]
      NetworkManager- alloc_fn: Storage is returned from allocation function "priority_map_new_from_str".
      NetworkManager- alloc_fn: Storage is returned from allocation function "g_malloc0".
      NetworkManager- var_assign: Assigning: "p" = "g_malloc0(8UL)".
      NetworkManager- return_alloc: Returning allocated memory "p".
      NetworkManager- var_assign: Assigning: "item" = storage returned from "priority_map_new_from_str(map, str)".
      NetworkManager- leaked_storage: Variable "item" going out of scope leaks the storage it points to.
      Error: RESOURCE_LEAK (CWE-772): [#def11]
      NetworkManager- alloc_fn: Storage is returned from allocation function "crypto_make_des_aes_key".
      NetworkManager- alloc_fn: Storage is returned from allocation function "g_malloc0".
      NetworkManager- var_assign: Assigning: "key" = "g_malloc0(digest_len + 1U)".
      NetworkManager- noescape: Resource "key" is not freed or pointed-to in function "crypto_md5_hash".
      NetworkManager- noescape: "crypto_md5_hash(char const *, gssize, char const *, gssize, char *, gsize)" does not free or save its pointer parameter "buffer".
      NetworkManager- return_alloc: Returning allocated memory "key".
      NetworkManager- var_assign: Assigning: "key" = storage returned from "crypto_make_des_aes_key("DES-EDE3-CBC", &salt[0], salt_len, in_password, &key_len, NULL)".
      NetworkManager- leaked_storage: Variable "key" going out of scope leaks the storage it points to.
  5. 05 Dec, 2014 3 commits
  6. 04 Dec, 2014 4 commits
  7. 25 Nov, 2014 1 commit
  8. 21 Nov, 2014 1 commit
  9. 19 Nov, 2014 1 commit
    • Dan Winship's avatar
      libnm, libnm-util: move settings doc generation to libnm-core · c1448698
      Dan Winship authored
      Move the settings/plugins doc generation from libnm-util to
      libnm-core, since libnm-util isn't being updated for all new
      With this commit, the keyfile and ifcfg-rh documentation is basically
      unchanged, except that deprecated properties are now gone, and new
      properties have been added, and the sections are in a different order.
      (generate-plugin-docs.pl just outputs the settings in Makefile order,
      and they were unsorted in libnm-util, but are sorted in libnm-core).
      The settings documentation used for nm-settings.5, the D-Bus API docs,
      and the nmcli help is changed a bit more at this point, and mostly for
      the worse, since the libnm-core setting properties don't match up with
      the D-Bus API as well as the libnm-util ones do. To be fixed...
      (I also removed the "plugins docs" line in each plugin docs comment
      block while moving them, since those blocks will be used for more than
      just plugins soon, and it's sort of obvious anyway.)
  10. 14 Nov, 2014 1 commit
    • Dan Winship's avatar
      docs: make the settings docs work from tarball builds · 16a9fc49
      Dan Winship authored
      docs/api/settings-spec.xml was accidentally not getting disted,
      because gtk-doc.make explicitly removes all DISTCLEANFILES from
      distdir. However, it doesn't actually make sense for the settings docs
      files to be in DISTCLEANFILES anyway; they were put there rather than
      CLEANFILES (IIRC) so that "make clean" in a tarball build wouldn't
      delete them and break things. But the right fix is to just make them
      only be in CLEANFILES when BUILD_SETTING_DOCS is true, and not ever
      get deleted otherwise.
      Also adjust the build rules to ensure that the generated docs don't
      get rebuilt in tarball builds, since that can cause problems when
      building from a read-only source tree, etc.
      Meanwhile, in an unrelated but also fatal bug, configure.ac's check
      for if the generated docs were already present never got updated for
      the cli/src -> clients/cli move, and so even if we had been disting
      settings-spec.xml, configure would still think that the tarball didn't
      have all of the generated docs in it, so SETTING_DOCS_AVAILABLE would
      be set false and none of the generated docs would get used.
  11. 13 Nov, 2014 3 commits
    • Dan Winship's avatar
      libnm*: fix library gettext usage · 53f5e9af
      Dan Winship authored
      Libraries need to include <gi18n-lib.h>, not <gi18n.h>, so that _()
      will get defined to "dgettext (GETTEXT_DOMAIN, string)" rather than
      "gettext (string)" (which will use the program's default domain, which
      works fine for programs in the NetworkManager tree, but not for
      external users). Likewise, we need to call bindtextdomain() so that
      gettext can find the translations if the library is installed in a
      different prefix from the program using it (and
      bind_textdomain_codeset(), so it will know the translations are in
      UTF-8 even if the locale isn't).
      (The fact that no one noticed this was broken before is because the
      libraries didn't really start returning useful translated strings much
      until 0.9.10, and none of the out-of-tree clients have been updated to
      actually show those strings to users yet.)
    • Dan Winship's avatar
      all: consistently include config.h · 3bfb163a
      Dan Winship authored
      config.h should be included from every .c file, and it should be
      included before any other include. Fix that.
      (As a side effect of how I did this, this also changes us to
      consistently use "config.h" rather than <config.h>. To the extent that
      it matters [which is not much], quotes are more correct anyway, since
      we're talking about a file in our own build tree, not a system
    • Jiří Klimeš's avatar
  12. 07 Nov, 2014 3 commits
  13. 29 Oct, 2014 1 commit
  14. 12 Oct, 2014 4 commits
    • Thomas Haller's avatar
    • Thomas Haller's avatar
    • Thomas Haller's avatar
      libnm-util: let nm_setting_diff() be symetric not to return properties that are set to default · 68bc95c1
      Thomas Haller authored
      Previously, nm_setting_diff() (and thus nm_connection_diff()), returned
      only properties that are different AND not set to the default value.
      However, if the opposite setting 'B' was missing, it would always
      include all properties from 'A', even the default ones.
      This behaviour was asymetric. Add two new compare flags
      behaviour of whether to include default properties.
      Signed-off-by: Thomas Haller's avatarThomas Haller <thaller@redhat.com>
    • Thomas Haller's avatar
      libnm-util: don't assert in nm_setting_get_secret_flags() and avoid assertion... · 978724da
      Thomas Haller authored
      libnm-util: don't assert in nm_setting_get_secret_flags() and avoid assertion in agent_secrets_done_cb()
      When secret providers return the connection hash in GetSecrets(),
      this hash should only contain secrets. However, some providers also
      return non-secret properties.
      for_each_secret() iterated over all entries of the @secrets hash
      and triggered the assertion in nm_setting_get_secret_flags() (see
      NM should not assert against user provided input. Change
      nm_setting_get_secret_flags() to silently return FALSE, if the property
      is not a secret.
      Indeed, handling of secrets is very different for NMSettingVpn and
      others. Hence nm_setting_get_secret_flags() has only an inconsistent
      behavior and we have to fix all call sites to do the right thing
      (depending on whether we have a VPN setting or not).
      Now for_each_secret() checks whether the property is a secret
      without hitting the assertion. Adjust all other calls of
      nm_setting_get_secret_flags(), to anticipate non-secret flags and
      assert/warn where appropriate.
      Also, agent_secrets_done_cb() clears now all non-secrets properties
      from the hash, using the new argument @remove_non_secrets when calling
        #0  0x0000003370c504e9 in g_logv () from /lib64/libglib-2.0.so.0
        #1  0x0000003370c5063f in g_log () from /lib64/libglib-2.0.so.0
        #2  0x00007fa4b0c1c156 in get_secret_flags (setting=0x1e3ac60, secret_name=0x1ea9180 "security", verify_secret=1, out_flags=0x7fff7507857c, error=0x0) at nm-setting.c:1091
        #3  0x00007fa4b0c1c2b2 in nm_setting_get_secret_flags (setting=0x1e3ac60, secret_name=0x1ea9180 "security", out_flags=0x7fff7507857c, error=0x0) at nm-setting.c:1124
        #4  0x0000000000463d03 in for_each_secret (connection=0x1deb2f0, secrets=0x1e9f860, callback=0x464f1b <has_system_owned_secrets>, callback_data=0x7fff7507865c) at settings/nm-settings-connection.c:203
        #5  0x000000000046525f in agent_secrets_done_cb (manager=0x1dddf50, call_id=1, agent_dbus_owner=0x1ddb9e0 ":1.39", agent_username=0x1e51710 "thom", agent_has_modify=1, setting_name=0x1e91f90 "802-11-wireless-security",
            flags=NM_SETTINGS_GET_SECRETS_FLAG_ALLOW_INTERACTION, secrets=0x1e9f860, error=0x0, user_data=0x1deb2f0, other_data2=0x477d61 <get_secrets_cb>, other_data3=0x1ea92a0) at settings/nm-settings-connection.c:757
        #6  0x00000000004dc4fd in get_complete_cb (parent=0x1ea6300, secrets=0x1e9f860, agent_dbus_owner=0x1ddb9e0 ":1.39", agent_username=0x1e51710 "thom", error=0x0, user_data=0x1dddf50) at settings/nm-agent-manager.c:1139
        #7  0x00000000004dab54 in req_complete_success (req=0x1ea6300, secrets=0x1e9f860, agent_dbus_owner=0x1ddb9e0 ":1.39", agent_uname=0x1e51710 "thom") at settings/nm-agent-manager.c:502
        #8  0x00000000004db86e in get_done_cb (agent=0x1e89530, call_id=0x1, secrets=0x1e9f860, error=0x0, user_data=0x1ea6300) at settings/nm-agent-manager.c:856
        #9  0x00000000004de9d0 in get_callback (proxy=0x1e47530, call=0x1, user_data=0x1ea10f0) at settings/nm-secret-agent.c:267
        #10 0x000000337380cad2 in complete_pending_call_and_unlock () from /lib64/libdbus-1.so.3
        #11 0x000000337380fdc1 in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
        #12 0x000000342800ad65 in message_queue_dispatch () from /lib64/libdbus-glib-1.so.2
        #13 0x0000003370c492a6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
        #14 0x0000003370c49628 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
        #15 0x0000003370c49a3a in g_main_loop_run () from /lib64/libglib-2.0.so.0
        #16 0x000000000042e5c6 in main (argc=1, argv=0x7fff75078e88) at main.c:644
      Signed-off-by: Thomas Haller's avatarThomas Haller <thaller@redhat.com>
  15. 03 Oct, 2014 1 commit
    • Dan Winship's avatar
      libnm-core: make NMSettingSerial:parity an enum · a91e6090
      Dan Winship authored
      NMSettingSerial:parity was defined as a char-typed property that could
      have the (case-sensitive!) values 'n', 'E', or 'o'. This is zany. Add
      an NMSettingSerialParity enum, and use that instead.
  16. 02 Oct, 2014 1 commit
  17. 04 Sep, 2014 2 commits
    • Dan Winship's avatar
      libnm-core, libnm-util: remove some useless code in nm-settings.c · 98e4a2be
      Dan Winship authored
      g_object_class_list_properties() can't return NULL if called
      Also remove two failed attempts to use g_value_transform():
      nm_setting_new_from_hash() was transforming src_value to its own type
      (rather than to param_spec->value_type, which was presumably
      intended), so it was a no-op (in addition to being unnecessary anyway,
      since GObject will attempt to transform the value internally if
      needed). And update_one_secret() was calling g_value_transform() on an
      uninitialized GValue, so it would have always hit a
      g_return_val_if_fail() in g_value_transform() if that code was ever
      reached (which apparently it wasn't).
    • Dan Winship's avatar
      libnm-util: generate-plugin-docs.pl-related fixes · 799922c1
      Dan Winship authored
      generate-plugin-docs.pl was assuming that it was being run out of
      srcdir, and so failed in srcdir!=builddir builds (such as "make
      distcheck"). Fix that.
      Also, update .gitignore
  18. 29 Aug, 2014 3 commits
  19. 22 Aug, 2014 3 commits
  20. 20 Aug, 2014 1 commit