shanepardue's dashboard

@bugreport: nice post, you've been doing some homework ;) – nmat, on July 16, 2008 15:25

Ok, that was convincing. Now I only need the source code to verify that my password remains at client...;-) – etu, on July 15, 2008 23:03

Ok, that was convincing. Now I only need the source code to verify that my password remains at client...;-) – etu, on July 15, 2008 23:03

There are different keys: one key for your "Cryptree" (best described as a "keyring") that is derived from your password that you enter on login with the username as salt and hashed 100 000 (?) times with SHA 256 to prevent bruteforcing + rainbow-tables and the passwords to decrypt the individual parts which are derived from the SHA256 hash of the parts. All the admins have is a encrypted file in wich all your keys to files you own + can access are, and this is encrypted with the Username + PW you enter at login. Luzius, please correct me if I'm wrong! ;-) – Bugreport, on July 15, 2008 07:27

How I know that the encryption key is not sent to the admins? Is the key derived from the (weak) password making it easy to make a brute force attack?

I noticed today that when I click and drag files into the Wuala java app, that replacing files that already exist cause the files to not copy correctly. If I delete the files on Wuala then move the files over, they work just fine. Could this be related to our syncing problem?

I'd be willing to use any kind of sync tool with Wuala..I really just want to have an easy way to backup my data to Wuala..Any working ideas?

Unison is great! One thing to note, I did use the "perms = 0" option within unison's profile system to disable the permission syncing, but I still run into a problem. It may have to do with the large number of files I'm trying to sync (approximately 40gb). – shanepardue, on June 02, 2008 14:53

Hi,
I tried unison on my ubuntu laptop. One problem is, that unison tries to change file permissions. This is currently not supported by our implementation. Unfortunately this is not a problem I can solve right now, although it would be nice to be able to syncronize with unison (I didn't know this nice tool before, thanks :)).

How would this be a problem associated with Wuala and not all NFS shares? I've tried multiple times trying different tactics such as increasing my cache size, but I still get "input/output" errors. This is the last thing I'd really love to see Wuala work properly with!

Its not required, you don't need to use update-alternatives, just edit your ~/.config/wualarc file and set JAVA to /usr/lib/jvm/ia32-java-1.5.0-sun/jre/bin/java. So you can keep java 64bit for everything else. – eth0, on May 27, 2008 10:05

I am on 64-bit HArdy and installed the 32-bit JRE:

sudo apt-get install ia32-sun-java5-bin

I then ran:

sudo update-alternatives --config java

to select the newly install JRE. I don't know if the last step is required but it certainly worked for me.

Sorry for using English. :(

McPop.

Well, that makes sense! ha..Thanks for the tip, got it working here also!

Just use 32bit java at your 64bit setup. Works here too.

This fix seems like a foreign language to me. Is there a way you could share a package or maybe explain it in layman's terms? This is the only program I'm missing with my 64-bit setup.

Thanks and sorry for the ignorance!

So, in my setup, I have a home PC running Ubuntu's AMD-64 distro, which is on a TWC IP; and I have 4-5 PCs at my office, sharing a single Verizon IP. Technically, I have two PCs at the office, one running Ubuntu amd64, the other with Windows XP; and the Ubuntu PC hosts a slew of Virtual Machines (Windows XP), two of which are always on. So, at the very least, 3 PCs and 2 VMs are always on--100% of the time. My home PC almost reached 17%, but it has been crawling backwards again. Over the past few days, I've lost ~0.5 percentage points a day, and I'm down to 12% average online time.

My office PCs have been losing percentage points more slowly--it's taken more than a week to drop from 10% to 8%. The VMs have never topped 5%.

Wuala is a life saver for me, because I can work from the same file system in any environment, bypassing VPNs and all the rest. I work from home quite a bit, and within my office, I have multiple simultaneous VPNs to different networks across the country, which makes Wuala a great solution. I just can't get over 17%. I've checked my network health on a daily basis--I'm not getting any significant packet loss or IP failures.

Is there any way to actually gain % for online time? I've been running Wuala for months with no sustained improvements in online average uptime.

hrm.

That's good to know. That means I can have multiple instances up on the same workstation using something like VirtualPC or VMWare and get credit for each instance of Wuala? I could divide up my upload between the multiple instances -- not contribute much upload as an average -- but get more storage. I guess someone needs to abuse the system for it to get fixed. :)

@ sunk818:
Each Wuala client generates a unique NodeID (it somehow looks like a IPv4 adress to me btw.) no matter what the extrernal IP is or was.

Wuala just does the following: Get the size of your ...\Wuala\Data\Fragments2 folder, multiply it by 10, compare it to your max. limit, take the lower value and multiply it with your uptime of that NodeID - that's it!
This is done on all your clients and the resulting size gets reported (btw. I'd say the calculation is done server-side!) and added to your account.

My guess is that if Wuala can see each workstation as originating from unique external IP addresses, each workstation would receive individual storage credit. You can combine those separate storage credit into one lump sum if use the same login for all the workstations.

If you have multiple workstations using the same external IP address, I could see that having unintended consequences.

Does Wuala currently factor in the following?

* Use actual KBs sent not related to initial-file upload. So, KB sent for maintaining and fielding requests are weighed.

* Sustained upload rate?

* Weigh Trade Up To less than it currently is. It is easy to trade up to 100GB and only contribute 10GB Locally Stored Data. It is a generous loophole right now.