Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenSync desktop synchronisation support #66

GoogleCodeExporter opened this issue Mar 14, 2015 · 5 comments

OpenSync desktop synchronisation support #66

GoogleCodeExporter opened this issue Mar 14, 2015 · 5 comments


Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

There are a huge number of issues open for import/export of file formats 
for other applications. I think it would be safe to assume that everyone 
would rather have their passwords kept in sync with their desktop 
application, rather than simply importing them and letting them diverge 
over time.

Fortunately, Secrets could solve both problems at the same time. If 
Secrets created an OpenSync ( conduit to convert 
Secrets files to/from a generic XML format, it would allow synchronisation 
of Secrets files with other Secrets files (over a number of transport 
options, such as USB, Bluetooth, WiFi). Secrets developers could then 
create conduits to convert the most important formats to/from the XML 
format. This would allow these formats to synchronise with other files in 
that format, or with the Secrets format, or any other formats that have a 

This approach may be slightly more work for the first format or two, but 
would have the epic advantage that it makes it increasingly attractive for 
other projects to write a converter to/from the XML format (perhaps to get 
support for KeePass), which would give Secrets that ability as well.

Original issue reported on by on 5 May 2010 at 2:25

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

This sounds like a good idea.  How would this be integrated into secrets?  
secrets link against a library that can parse the xml files, or would secrets 
the files itself?

Can you provide an example xml file that would be used for password management 


Original comment by on 22 May 2010 at 3:42

  • Added labels: Type-Enhancement, Priority-Low, Import
  • Removed labels: Type-Defect, Priority-Medium

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

Original comment by on 22 May 2010 at 4:14

  • Changed state: Accepted

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

My understanding is that there is a libopensync, so Secrets would need to write 
plugin that converts from Secrets format to something more generic.

I don't know a lot about the technical aspects, but I don't think that any other
password programs use OpenSync -- probably because no others use it yet.

I would expect that the OpenSync devs would be keen to help you do this. The 
list is

Original comment by on 7 Jun 2010 at 8:41

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

I can only hope you're not thinking about adding a network sync. I really that 
warm fuzzy feeling of safety when the application I use to store some of my 
secrets does not even have the permission to send anything over the network.

We can argue that it's an open source app, so everybody would see if it was 
doing something wrong, but network access would still make me feel uneasy. In 
the end it's not like someone is screening every update?

Paranoid? Maybe a bit. But there's plenty of other applications that support 
more or less elaborate synchronisation scenarios. Personally, I like the 
simplicity of this application as is — just stores stuff, and exports them on 
the card, if you ask it to. I hope such option will stay there forever.

Original comment by on 24 Oct 2010 at 9:13

Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 14, 2015

Hi pitkali,

You are not paranoid, nor are you alone in getting that warm and fuzzy feeling 
about apps that don't have internet access.  At this point internet access is 
not a permission that Secrets will ever ask for.

Sync'ing with the "desktop" is something that lots of people have asked for 
though, and even I sometimes wished there was something like that.  I've been 
thinking about a solution to this problem for a little while now (and because 
of these security issues I'm moving deliberately slowly).  The solution is 
along the lines of installing a second, totally separate app that privately 
communicates with Secrets and syncs with some online service (not a desktop).

The bottom line then is this: those who don't need sync'ing can install Secrets 
only, with no ability for your secrets to reach the internet.  Those who want 
sync'ing would need to install another app as well, with the knowledge that 
this configuration will send your secrets to an online destination of their 

Does this still give you that warm and fuzzy feeling?

Original comment by on 24 Oct 2010 at 2:01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant