All releases of Remote Gnu Database Manager

  •  27 Jun 2007 05:32
Avatar

    Release Notes: A segmentation fault in gdbmsql when started with no options has been fixed. Various minor fixes to the "debian" subdirectory files have been implemented. There is now a sysv-init startup file for the daemon.

    •  25 Jun 2007 11:17
    Avatar

      Release Notes: The "debian" subdirectory has been added to the tar archive so an extra patch is no longer needed in order to build the deb (and hence rpm) packages from the archive source.

      •  21 Jun 2007 10:38
      Avatar

        Release Notes: This release fixed a problem where the server working and certificate directory locations would have been mangled if configure was run without --localstatedir=/var. This release also compiles even without gdbm and can use ndbm and Berkeley dbm databases on platforms without GNU gdbm.

        •  20 Jun 2007 14:12
        Avatar

          Release Notes: Support for old ndbm and dbm format databases has been added at the server end. It should be invisible to the client.

          •  18 Jun 2007 20:39
          Avatar

            Release Notes: Minor changes have been made to help compilation on DOS-derived platforms (e.g. renaming "aux.c" to "sup.c").

            •  16 Jun 2007 19:32
            Avatar

              Release Notes: A terminal query language shell has been added to the archive (in the contrib directory). It is convenient for remote manual administration of a gdbm database area.

              •  15 Jun 2007 17:39
              Avatar

                Release Notes: Error message and error number interchanges have been fixed.

                •  13 Jun 2007 17:30
                Avatar

                  Release Notes: This release fixes a hang after disconnecting in the server daemon due to undead sockets that weren't shut down properly. It fixes a related socket leak in the parent server daemon, which would have died after 1024 sessions.

                  •  11 Jun 2007 12:20
                  Avatar

                    Release Notes: SSL is now used as the network transport by default, thus hiding all data from attackers. The server will handle both SSL and plain TCP connections. The client library can choose which to use per session. Without SSL, data goes over the net unencrypted. If the server is going to offer SSL, it needs a certificate in its /var/lib/gdbm/certs/gdbmd.crt. The certificate had better be signed by some CA that the client knows about via its /etc/ssl/certs directory. If the certificate is self-signed, that implies updating both areas.

                    •  11 Jun 2007 12:18
                    Avatar

                      Release Notes: Passwords (if used) have been made safer by using a zero information interchange based on the encrypted password as the shared secret known only to server and client.

                      Screenshot

                      Project Spotlight

                      episoder

                      A tool to tell you about new episodes of your favourite TV shows.

                      Screenshot

                      Project Spotlight

                      BalanceNG

                      A modern software IP load balancer.