MaidSafe Dev Update :safe: 24th May 2016

[Nigel]

@Ross

We are also planning to drop the encryption between the applications and the launcher

This is strictly for pre release testing correct?

[Nigel]

That’s enough for me and I think it should satisfy others as well, thanks Nick

[Ross]

@Nigel

This is strictly for pre release testing correct?

Honestly I am not 100% sure - @Krishna_Kumar can you clarify this please?

[19eddyjohn75]

Thanks for the update Maidsafe team,

I’m sorry on test 3, I still didn’t manage to run a vault (only demo app + launcher )

Maybe test 4, somebody can make a how to video

Thank you also to the hardheaded kids, who stay around on this playground

[Blindsite2k]

@Nigel

So a chunked malicious program that may be subject to data loss on a testnet is going to steal my identity? Solution use a clean computer or encrypt all of said important private information

I’m not so much concerned about the testnet as people wouldn’t, or shouldn’t at least, be storing any valuable on it anyway. But it is a vunerability to be aware of a sealed up before beta and final release.

@mvanzyl

Anything that hits the network or is in transit to the network will still be encrypted locally before it goes out as I understand it.

Anything you have stored on the network such as credit card info or safecoins will always be encrypted. (does not travel between the app and the launcher that is part of the proposed unencrypted data)

Vaults will be encrypted always so that will not be an issue and there will only be chunks not whole files stored there.

We may want to check with @Ross to see specifically what would be left unencrypted if this option is chosen…

Okay this is a bit of a releaf and yes clarification would probably help immensely.

[cretz]

@Ross

We are also planning to drop the encryption between the applications and the launcher.

Rejoice! If the subject does come up again (as opposed to how it’s used now which is essentially named pipes for IPC but in HTTP form) just know there are TLS approaches that can be taken.

Now the next step is to remove the unnecessary base64’ing (HTTP is a byte-based protocol, not a text based one). Then finally, make sure the benefits of HTTP streaming are used (e.g. if I download a 1G file over the launcher, it isn’t loading it all in memory or something). I mentioned another couple of things at Safe Launcher Dev Issues/Suggestions but in general this is a great improvement for performance and idiomatic HTTP usage. Thanks!

[bluebird]

@19eddyjohn75

Thanks for the update Maidsafe team,

I’m sorry on test 3, I still didn’t manage to run a vault (only demo app + launcher )

Maybe test 4, somebody can make a how to video

Thank you also to the hardheaded kids, who stay around on this playground

What platform are you on?

[Frontrow_Al]

hmmmm, I’m now wondering what I did to think I was running a vault, I’m on windows 10 and just double clicked the vault exe and that was it, I think that was running a vault, thinking it wasn’t now, everything else was double click though…

cheers
Al

[Krisjanis_Gross]

Thank You for the update! Much appreciated!

[Krishna]

@Nigel

This is strictly for pre release testing correct?

No, this would be the way moving forward. This is just a proposal at this point and also seems to be legit to take that route.

The data transfer is very much encrypted in the network layers. The data is encrypted when it leaves your machine. We are proposing to drop the encryption that happens locally between the applications and the launcher.
Since the applications and the launcher are running on the same machine, having a session based encryption just for the data transfer between local applications is a mere overhead.

[Krishna]

@polpolrene

I’ve added some bugs with the Demo app, but I don’t know if they belong to the Launcher or to the Demo app.

We will take the issues raised in the demo app along with the launcher. My assumption is that the issues #65 and #66 are likely to be related to the 5MB issue raised in the safe_launcher. Will update the issue as soon as it is fixed.Thanks @polpolrene

[19eddyjohn75]

@bluebird

What platform are you on?

Hi Bluebird,

Sorry for my late reply, I’m on Ubuntu 15.10.

Like @Frontrow_Al I double clicked the vault exe, but I didn’t really get the impression that that was doing the job. I’m sure a lot more people would join these play around rounds if they only had some one do a step by step.

@bluebird thank you for being on the frontier and experimenting with the network like this.

[gonefarmin]

For what it’s worth, I tried running a local vault on my Ubuntu machine last week, and it generated a couldn’t run error. I suspect it was because I didn’t set the config file correctly. Anyway, I’ll try that again in TN4, or in the community_run_net. The launcher worked flawlessly in TN2 (Win7) and TN3 (Ubuntu) for me.

[anon40790172]

@Krishna_Kumar

My assumption is that the issues #65 and #66 are likely to be related to the 5MB issue

Thanks for the reply, but to be clear, the problem also shows up when I try to upload files <5mb. 1 by 1 to the network. Without hitting any limits for accountsize or filesize.

[Arcturus]

Right click on the vault folder and choose open in terminal. Then type ./safe_vault in the terminal and it should start

[abittner]

Reminds me somewhat of Freenetproject, they have the users webbrowser as a main gui to the Freenet core daemon running on the local machine and for example exposing a webserver on localhost. But there is still a TLS option to fetch those pages from localhost via the webbrowser but which the user can opt in or out at free will. They have a password option to unlock the webserver, but the TLS layer is still in addition to that.

[Krishna]

The size of the file increases when it gets stored in the network because of the file getting encrypted and saved as chunks. Though we consider it has 4 Mb file, the actual size in the network can be higher. This is an assumption as I said earlier, will definitely need to check to confirm the same.

[Artiscience]

@19eddyjohn75

Sorry for my late reply, I’m on Ubuntu 15.10.

Like @Frontrow_Al I double clicked the vault exe

Well, to be fair, @Frontrow_AI was on Windows. By saying exe you mean executable or did you emulate the Windows package.

[19eddyjohn75]

No I didn’t use wine, I’ll try the above

Thanks

[hillbicks]

What about a usecase where the user wants to run the vault permanently on a headless server and connect the launcher to it from a separate machine? In this case, encryption would be good to have, even necessary.