Mageia forum

I'm looking for alternative to Dropbox, which works not so good with Mageia.
So I've found Mega Sync -> https://mega.co.nz/ - they give 50GB storage for free.
Sync Client is available as rpm package, unfortunately only for Fedora and OpenSuse.
I've tried to install Fedora 19 rpm package on Cauldron but without success (it needs libssl.so.10 library).

Did anybody managed to run Mega Sync Client on Mageia?

napcok wrote:I'm looking for alternative to Dropbox, which works not so good with Mageia.

Hmm, works fine here. Care to elaborate?

napcok wrote:I've tried to install Fedora 19 rpm package on Cauldron but without success (it needs libssl.so.10 library).

Did anybody managed to run Mega Sync Client on Mageia?

You can easily install via urpmi --allow-nodeps (run multiple times, once to install depdencies, and another time to try to install it and answer "y" when it asks to try to do an install ignoring dependency issues)
Or directly via

Code: Select all

urpmi --allow-nodeps --allow-force

(does not install other dependencies beforehand)

Then create a symlink to libssl.so.10 which the program expects, pointing to the real libssl.

Was curious, just created an account there and installed the client. First time to only install dependencies:

Code: Select all

[doktor5000@Mageia4 ~]$ sudo LC_ALL=C urpmi --allow-nodeps https://mega.co.nz/linux/MEGAsync/Fedora_20/x86_64/megasync-Fedora_20.x86_64.rpm
WARNING: --allow-nodeps option is in use. Some strange problems may happen
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch   
(medium "Core Release (distrib1)")
  lib64cryptopp6                 5.6.2        2.mga4        x86_64 
(command line)
  megasync                       1.0.31       1.1           x86_64 
8.7MB of additional disk space will be used.
2.4MB of packages will be retrieved.
Proceed with the installation of the 2 packages? (Y/n) Y


    http://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/4/x86_64/media/core/release/lib64cryptopp6-5.6.2-2.mga4.x86_64.rpm
installing lib64cryptopp6-5.6.2-2.mga4.x86_64.rpm from /var/cache/urpmi/rpms                                                                                           
Preparing...                     #####################################################################################################################################
      1/2: lib64cryptopp6        #####################################################################################################################################

Ran a second time to actually install it:

Code: Select all

[doktor5000@Mageia4 ~]$ sudo LC_ALL=C urpmi --allow-nodeps https://mega.co.nz/linux/MEGAsync/Fedora_20/x86_64/megasync-Fedora_20.x86_64.rpm
WARNING: --allow-nodeps option is in use. Some strange problems may happen


warning: /var/cache/urpmi/partial/megasync-Fedora_20.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 4d70f67a: NOKEY
The following package has bad signature:
/var/cache/urpmi/partial/megasync-Fedora_20.x86_64.rpm: Invalid signature (NOT OK (no key): /var/cache/urpmi/partial/megasync-Fedora_20.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 4d70f67a: NOKEY)
Do you want to continue installation ? (y/N) y
installing megasync-Fedora_20.x86_64.rpm from /var/cache/urpmi/partial
Installation failed:                                                                                                                                                   
        libcrypto.so.10()(64bit) is needed by megasync-1.0.31-1.1.x86_64                                                                                               
        libcrypto.so.10(OPENSSL_1.0.1)(64bit) is needed by megasync-1.0.31-1.1.x86_64                                                                                   
        libcrypto.so.10(libcrypto.so.10)(64bit) is needed by megasync-1.0.31-1.1.x86_64                                                                                 
        libssl.so.10()(64bit) is needed by megasync-1.0.31-1.1.x86_64
        libssl.so.10(libssl.so.10)(64bit) is needed by megasync-1.0.31-1.1.x86_64
Try installation without checking dependencies? (y/N) y
Preparing...                     #####################################################################################################################################
      1/1: megasync              #####################################################################################################################################
error: /tmp/megasync.B0sNvc: key 1 not an armored public key.
[doktor5000@Mageia4 ~]$ rpm -q megasync
megasync-1.0.31-1.1
[doktor5000@Mageia4 ~]$

And two symlinks later the client is running, as root run:

Code: Select all

ln -s /usr/$(rpm -E %_lib)/libssl.so.1.0.0 /usr/$(rpm -E %_lib)/libssl.so.10
ln -s /usr/$(rpm -E %_lib)/libcrypto.so.1.0.0 /usr/$(rpm -E %_lib)/libcrypto.so.10

Command should work both for i586 and 64bit. Libraries (libopenssl) can be installed via

Code: Select all

urpmi libssl.so.1.0.0 libcrypto.so.1.0.0

Thank you so much doktor5000
It works now

napcok wrote:Thank you so much doktor5000
It works now

Why did you mark the thread as [DONE] which suggests that you gave up rather than [SOLVED]?

I've adjusted the thread title a little bit now, and also moved the thread to tips&tricks subforum in between.

fyi:

http://www.3news.co.nz/technology/revie ... 2013012213

particularly : "Part of Mega's setup is that all encryption takes place in the browser and the company doesn't have access to your encryption keys, preventing them from knowing the content of your files. So if you lose access to your account by forgetting your password, which is also your master key, you're out of luck."

And despite not being able to see what users have uploaded, Mega says if an uploaded file matches one already uploaded by another user, it may be deleted automatically. Your account will instead access the one uploaded earlier. This is common on other storage services, but Mr Vaughan-Nichols said it's a strange claim to make since "Mega also only stores encrypted files and the company states that it doesn't have access to your encryption key".

Uhmm, why do you install some arbitrary crypto libraries for which you won't receive any updates?
I wonder why I posted how to install the client a few posts further up ...