Tsu

Members
  • Posts

    9
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Tsu

  1. But that is in case of someone actually trying to crack my e-mail or Dropbox account. They can't access my e-mail account my random luck because a username and password match has to be made. In the case of a secret they only need to randomly get the same secret as me. Chances are slim but they do exist right?

  2. Not if the length of Secrets was improved - I'd like to see someone try crack a secret of length of let's say 512 characters (including symbols!) - rather than just the current 21 alpha-numeric character secrets!

    Problem is that they don't need to crack, can be an unlucky collision. Chances are small but they are still there if there is no way to guarantee a unique secret.

    For this to work, the service would rely on a connection to BitTorrent, and your details stored there in a database! I would suggest that this is actually LESS secure than being responsible for your own unique secrets that only you generate and use.

    The whole point of SyncApp is that it doesn't require a central server (or any connection to the internet for that matter - you can sync directly accross a LAN!)

    But how does SyncApp know which computer has the files beloning to my secret? If I enter my secret on another computer the original computers need to know what computer was added and how to reach that computer.

    And it wouldn't be less secure if it used two secrets. Compare it to having an account for each computer to log on to and from which to manage sharing folders with other accounts and a seperate secret that is also needed to access folders but isn't stored centrally.

    As I said previously, SyncApp needs to be both secure AND user-friendly. I don't think users would like the idea of their secrets being "checked against a master database at BitTorrent" as it were... and beside I still don't see the need for this as long as SyncApp removes the current 21 alpha-numeric limit on secrets, to allow you to generate/manually enter secrets of any length, and include symbols as well. Seriously, it would take decades for the best super computers in the world to "guess" an extremely long secret!

    It will take decades for a super computer to guess that specific secret but it can take but a second for a random computer to accidentally generate a secret that is allready in use somewhere else. Give a thousand monkeys a thousand typewriters and there will be a day when a monkey writes Hamlet.

    With no guarantee that a secret is unique there will always be a change, however small, that someone will get your files.

  3. That seems a bit over the top IMO - If you think back to the very recent days of Windows Live Mesh, when you consider all you needed was someone's email address and their Live password and you'd then have full access to all their Mesh'd files, their SkyDrive, and Remote Access to their sync'd devices - no-one questioned the poor security that just a simple password provided for Mesh!

    I agree that the "secrets" system for SyncApp does have some big drawbacks at present, however, I believe that if they removed the current fixed-length size limit on secrets, allowing users to enter/generate a key of much greater/any length, as well as permit symbols along with numbers and letters - this would make "secrets" extremely secure indeed - it would take the fastest super-computers centurys to crack a very long "secrets" then!

    The problem with secrets is that you can "crack" them without trying. It's perfectly possible that two users can end up with the same secret and thus see eachothers files. Ofcourse the chances are slim, but they do exist. Rather than creating stronger secrets where the collision chances are reduced I would like to see a system where there are two secrets and you need them both to access files. The first secret is generated by Bittorrent and is checked against a database to make sure it's unique. The other is user generated and doesn't need to be unique. Same as a username and password except the username is just a random string.

  4. As I posted in the other topic as well:

    Hmm, still not working to be honest.

    I do get this now:

    [2013-02-28 16:21:29] Sending broadcast ping for folder E:\*foldername*

    [2013-02-28 16:21:29] Send ping to peer (0000000000000000000000000000000000000000) for folder E:\*foldername*

    [2013-02-28 16:21:29] ping *IP server*:11111 directly

    [2013-02-28 16:21:29] ping *IP server*:11111 via relay

    After a few days still nothing happening.

  5. Hmm, still not working to be honest.

    I do get this now:

    [2013-02-28 16:21:29] Sending broadcast ping for folder E:\*foldername*

    [2013-02-28 16:21:29] Send ping to peer (0000000000000000000000000000000000000000) for folder E:\*foldername*

    [2013-02-28 16:21:29] ping *IP server*:11111 directly

    [2013-02-28 16:21:29] ping *IP server*:11111 via relay

  6. Hi,

    I can't get Sync to start when I'm on the corporate network. I use a network that has no firewall protection and all my other apps can connect just fine.

    I defined a custom host, added exceptions to the firewall on my laptop and.. nothing.

    It's a Windows 7 laptop and the other online client is a Windows 2008 R2 server.

    The folder I am trying to sync is a Truecrypt file mapped to a local disk, I am syncing that local disk so the application can see the individual files.

    Log:

    [2013-02-26 10:09:25] Loading config file version 1.0.75

    [2013-02-26 10:09:25] Loaded folder E:\Foldername