kos13
-
Posts
750 -
Joined
-
Last visited
-
Days Won
92
Posts posted by kos13
-
-
We have updated FAQ http://help.getsync.com/customer/portal/articles/2113928
Q: If I purchase a non-subscription license for personal use, does this include product updates and upgrades?
A: Non-subscription Sync Pro licenses include all product updates within a given product version.
Upgrade releases contain functional enhancements and must be purchased separately unless you have an active subscription license.
-
Every NAS vendor has his own rules, so it takes a while to update packages. Please wait, it should be updated shortly.
-
@garrily Sync crashed, so debug logs won't help here. I hope you are using the latest build that is 2.2.1. If not, try to download it from the site.
Follow the part how to create OS X dumps. When you will create the dump, you will need to send it to us. You could reply to this ticket with the link and reference to this post.
http://help.getsync.com/customer/portal/articles/2100441
Thanks
kos
-
@calvyb You should upgrade machines to 2.2 to use new license.
-
@hopkins. Could you also PM me your e-mail, we will address MS Access issue.
-
@lupus. Could you please PM me your e-mail. I will make sure your issue will be addressed.
thanks
kos
-
@kramttocs You look for FAQ clarification, or have another question that is related to it? Sorry, I can't find what exactly needs to be clarified.
-
@alin All 2.2-2.x releases will be covered by this license.
-
@kamborio: We are going to look why 2.2 didn't fix your issue. I think RomanZ has your direct e-mail, if not, could you please PM it to me? This way we could speed up communication.
Thank you,
kos
-
Sync is and was always backward compatible. 2.x works with 1.4, 1.3, 1.2.
2.x will work with 3.x
-
the .sync directory off of where you run the executable from
-
Yes these are the steps. But I would also backup Sync config folder, just in case.
kos
-
I will try to answer your questions and I hope that answer will address your concerns. You have two separate questions: one is related to the quality of software and another about Sync business model and its changes.
Sync quality. As you could see from change logs for every release the team spends significant effort to address issues that are found. It is a constant effort that involves not only developers, QA engineers and support team but also the community. As you could see from the forum people are using Sync in quite a variety of OS/machines/networks configuration. The help of Sync community is an important aspect for making Sync better. We listen to the community and respect everyone's input and efforts, without your help we wouldn't be where we are.
Sync business model. We made this decision based on what we've learned since launch. We may never make everyone happy. But we are working hard to build a business and make an awesome product. We'll continue to share in the forums and elsewhere as Sync continues to evolve.
kos
-
Thank you for reporting, we are going to fix it.
kos
-
@eldrin I just wanted to ensure you that you've got the right license and you have nothing to worry. And thank you for your report, developers are working on the fix. We forgot to push this page.
-
-
The consumer license does have the expiry date January 1, 2038. This implies forever license to Sync.
-
Device-based permissions. It is Read-write and read-only permissions that are based on key (secrets).
User-based permissions. It is Read-write, read-only and owner permissions based on certificates.
-
Should be working now.
-
Your two machines have the same time, right?
-
Yet you chose not to replicate file permissions across platforms?
So files and folders with strict security permissions are replicated without any permissions what so ever
It was an interesting discussion a while back, but let me explain why it wasn't solvable in 1.x releases. First of all you will need to synchronize file uid/gid together with permissions. Which might be fine, if there are two machines that are owned by you and you are guarantee that users/groups are identical between these machines. Majority of users will not be able to do that and this will lead to a complete mess. And keep in mind Linux -> Win/MAC synchronization.
This was simple usability problem, rather than technical.
I can't see much benefit in the new "link" approval system in terms of security.Links solves two problems:
- Eliminate need of transferring keys over insecure media such as e-mails.
- Better usability for first time users. Now I could share folders with my mother
Which doesn't sound like a big security thing, however I am sure she won't be able to handle folder keys properly and might expose it. So this is a security improvement too.- Links were a first step towards new certificate based model, that is fully implemented in Sync 2.0. This model gives us granular control over permissions with the ability to revoke and change it on the fly.
kos
-
I hope you saw a Sync 2.0. You could now granularly control user access for a folder. Some of the ideas are already implemented, but not all of them. I also want to point out, that Sync uses X509 based PKI security to achieve that. Cost of that - there are no keys for new folders.
-
Jake,
My devices is designed in a way that you have ability to add folder, that is added on different computer. Folder is not added, nor data is transferred. This is default behavior. In preferences you could change it, so folder will be added in Connected (only placeholders will be added) or Synced (All data will be synchronized). Just go to My Devices | This device
If you have a much complex environment, you could use links and don't join devices via My Devices.
kos
-
You could just copy an "http://link.getsync.com....." link to "Manual connection" instead of key. It is slightly longer than a key, but at the same time it doesn't have any private information.
Which doesn't sound like a big security thing, however I am sure she won't be able to handle folder keys properly and might expose it. So this is a security improvement too.
Introducing Sync 2.2
in Sync General Discussion
Posted
@kaz911. Thank you for report!!!