← Back to team overview

nssbackup-team team mailing list archive

Re: sbackup

 

Hello Tim,

Tim Johnson a écrit :
Omar:

Thanks for you response. I was unable to find the 0.2 version on Launchpad (probably a personal problem). For now, I just downloaded 0.1-6.


No, it was not your fault to not find it there. In fact I use to upload the package in the PPA so that it's easily installable on Ubuntu by I always forget to add it to the project Download files. I just added the 0.2 beta 5 . You might want to check this one out.

The good news is my employer encourages us to contribute to Open Source. They even say it is important, but not urgent.

The two changes I would like to see and would be willing to contribute:

   1. The password for the 'ssh' backup is stored unecrypted in the
      nssbackup.conf file. I can think of a number of ways to fix this
      problem. You may want to talk about what make sense to you. At the
      very least I would be will to document how to get 'ssh' working
      without a password

For ssh I use Fuse sshfs in NSsbackup. One possibility to hide the password is to encrypt it in the configuration file and make NSsbackup decrypt it for usage. The problem with this is : the crypting is symmetric. So the value of the password can be guessed.

Another way is to use ssh without password. Maybe provide a GUI to help the user putting this in place.


   2. When a 'backup now' run there should be some way to let the user
      know that  the backup in 'in-prgress'. When completed a 'Done
      popup' should appear and 'wait()' should be called on the child
      'backup' process. The way it works currently is pretty clunky and
      based upon support questions is a source of confusion. By the way
      I have not yet checked to see is this was changed in nssbackup
      (maybe in 0.2?).

For NSsbackup, I have make use of libnotify which created some notification message. For the moment, it just show 3 messages :
One at the beginining
One before launching Tar
One after the backup

There will be also a message in case of crash. For the next version I am developing an API to allow easy use of that and to be able to configure the notification level.

Reading your idea, I think it can also be cool to have an icon in the notification area when NSsbackup is running.


The good news is my employer encourages me to contribute to Open Source. They even say it is important, but not urgent.



------------------------------------------------------------------------
Tim Johnson Scuba Diver (503) 629-8625 (Home) (503) 757-9012 (Cell)

Oumar Aziz OUATTARA wrote:
Tim Johnson a écrit :
All:

What is the state of development for 'sbackup'? I really see a need for a backup tool such as 'sbackup'. It meets the needs for a large number of user's/situations. I have used other tools (such as backupPC) that clearly address a different audience/situation.

I would be willing allocate some time to support 'sbackup'. I have a 25 years of development experience in Unix/Linux and several years of experience with python. I have a desire to broaden my experience with Glade and Python.

I have been using 'sbackup' for some time now. I have made some local changes to sbackup that I would love to share with the rest of the user community. I think there is actually a fairly large number of people using sbackup.


Hello,

This is quite interesting. Actually, Aigars is the most active one supporting sbackup. I, in my side, have forked it into NSsbcakup. But the goal was to move NSsbackup back to sbackup. NSsbackup is in version 0.2 and I wanted to move NSsbackup to sbackup in version 0.3 .
Problem is, I am lacking some motivation here :-( .

Here is where the NSsbackup project stored.
https://edge.launchpad.net/nssbackup

I have implemented new functionalities in NSsbackup that was needed and requested from the users. Then what I am interested in, is to know what changes you have made in Sbackup and how those could be integrated.

Best Regards
wattazoum



Attachment: signature.asc
Description: OpenPGP digital signature