cancel
Showing results for 
Search instead for 
Did you mean: 

Feasibility of RPi as fileserver to avoid ransomware?

ReedRichards
Seasoned Pro
Posts: 4,927
Thanks: 145
Fixes: 25
Registered: ‎14-07-2009

Re: Feasibility of RPi as fileserver to avoid ransomware?

Pity there isn't a common name for the 'index'.  By all accounts the latest ransomware trashes the index and only pretends that it can be recovered by paying a ransom.  All the references I have read say that it encrypts the MFT so does that mean that a Linux file server would be unaffected?  Or an exFAT partition on Windows? 

7up
Community Veteran
Posts: 15,830
Thanks: 1,587
Fixes: 17
Registered: ‎01-08-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?

Well that was my thinking RR - that a disk hosted on another OS would be safe...

I need a new signature... i'm bored of the old one!
Anonymous
Not applicable

Re: Feasibility of RPi as fileserver to avoid ransomware?

The majority of ransomware is written in C and targetted at Windows due to the user base and is downloaded to the victim via JS. If the author is interested in trashing anything else that is found on the network that is easily done by downloading an executable for the OS in question. But in order to trash a Linux system an exploit would need to exist on the target OS that allowed for root escalation, but maybe having the home directory compromised would be enough.

With the many variants of Linux / Unix out there this is easier said than done and would more than likely need to be a kernel based exploit to make it worth while for the author to code it.

That’s not to say it isn’t possible, after all SMB is a core component of Windows. However with the way that code is written for Linux it is reviewed and tested by the authors’ peers prior to release and most screamers are caught and fixed. But that alone does not make it immune.

It is likely in fact, highly likely, that ransomware for Linux will be more prevalent in the future, but for my money (bitcoins accepted) I suspect the next major victim will be Android phones.

Alex
Community Veteran
Posts: 5,500
Thanks: 921
Fixes: 13
Registered: ‎05-04-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?

I wonder if you can setup some kind of automatic replication, so as soon as you save a file on one device, it goes to the other. So both are always up to date?
VileReynard
Hero
Posts: 12,616
Thanks: 582
Fixes: 20
Registered: ‎01-09-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?

Consider inotify...

INOTIFY(7)                                          Linux Programmer's Manual                                         INOTIFY(7)

NAME
       inotify - monitoring filesystem events

DESCRIPTION
       The  inotify API provides a mechanism for monitoring filesystem events.  Inotify can be used to monitor individual files, or to monitor directories.  When a directory is monitored, inotify will return events for the directory itself,  and  for files inside the directory.

       The following system calls are used with this API:

       *  inotify_init(2) creates an inotify instance and returns a file descriptor referring to the inotify instance.  The more recent inotify_init1(2) is like inotify_init(2), but has a flags argument that provides access to some extra function‐ality.

       *  inotify_add_watch(2)  manipulates  the  "watch  list" associated with an inotify instance.  Each item ("watch") in the watch list specifies the pathname of a file or directory, along with some set of events that the kernel should monitor for  the  file  referred  to  by  that pathname.  inotify_add_watch(2) either creates a new watch item, or modifies an existing watch.  Each watch has a unique "watch descriptor", an integer  returned  by  inotify_add_watch(2)  when  the watch is created.

       *  When  events  occur  for monitored files and directories, those events are made available to the application as structured data that can be read from the inotify file descriptor using read(2) (see below).

etc, etc....

or you could just set up a RAID array. Funny

 

 

"In The Beginning Was The Word, And The Word Was Aardvark."

7up
Community Veteran
Posts: 15,830
Thanks: 1,587
Fixes: 17
Registered: ‎01-08-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?

 

@Anonymous wrote:

The majority of ransomware is written in C and targetted at Windows due to the user base and is downloaded to the victim via JS..


It was my understanding that javascript could not touch the users file system so how is that done then?

As far as i'm aware most drive by downloads are actually powered by flash which does have the ability to play filing cabinets..

I need a new signature... i'm bored of the old one!
Anonymous
Not applicable

Re: Feasibility of RPi as fileserver to avoid ransomware?

I am no expert in this so maybe the choice of wording could have been better as there are of course other means of delivery, but I mentioned JS as the majority of users will have this enabled by default.

MauriceC
Resting Legend
Posts: 4,085
Thanks: 929
Fixes: 17
Registered: ‎10-04-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?


@Alex wrote:
I wonder if you can setup some kind of automatic replication, so as soon as you save a file on one device, it goes to the other. So both are always up to date?

You could set up DFS (Distributed File Server) on Microsoft Server 2003R2 - or later to do this.  But it is still Microsoft and I think still uses SMB, so solve one problem and gain a few more!

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Alex
Community Veteran
Posts: 5,500
Thanks: 921
Fixes: 13
Registered: ‎05-04-2007

Re: Feasibility of RPi as fileserver to avoid ransomware?

Yes, sadly the only way I think to go is to use CD/DVD/Blu Ray media. Keep it wherever in the house.

The hackers will find some other exploit in the future, and now they've learnt it makes them money it will continue. It wouldn't surprise me if they share the source code with each other and adapt it for the next one.