Difference between pages "Mobile malware" and "Talk:Linux Logical Volume Manager (LVM)"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
m
 
(Created page with "Should we change :To make the volume group known to the system :vgexport $VOLUMEGROUP to :To make the volume group known to the system :vgimport $VOLUMEGROUP ? vgexport ma...")
 
Line 1: Line 1:
Mobile malware is software created to infect or gain access mobile devices such as [[cell phones]], [[tablets]], and [[PDAs]].
+
Should we change
  
== History ==
+
:To make the volume group known to the system
Mobile malware was initially considered to be a hoax until it became obvious this malicious software existed and functioned. The earliest recorded mobile malware was called Cabir. It was released in 2004 and was designed to infect [[Symbian]] OS platforms via a Bluetooth connection. It was essentially harmless, but nonetheless proved to the public that worms could be found on mobile devices.
+
:vgexport $VOLUMEGROUP
  
== Recent Trends==
+
to
Since mobile devices usually contain private and valuable information, mobile malware has recently began moving toward having a specific purpose (usually exploiting information) as opposed to viruses created solely for bragging rights.
+
  
== External Links ==
+
:To make the volume group known to the system
[http://safeandsavvy.f-secure.com/2011/06/14/a-quick-guide-to-mobile-malware-part-1-2/ A Quick Guide To Mobile Malware]
+
:vgimport $VOLUMEGROUP
 +
?
  
[http://www.cs.berkeley.edu/~afelt/mobilemalware.pdf A Survey of Mobile Malware in the Wild]
+
vgexport makes volume groups ''unknown'' to the system, vgimport makes exported volumes ''known'' to the system. See also [http://www.tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html this]. You should also remember, that both vgexport/vgimport alter the data on the physical device. I also added "loop" option to the mount command example, since "-o ro" may alter the data in the file system (replay the journal, etc) [[User:.FUF|.FUF]] ([[User talk:.FUF|talk]]) 10:19, 7 May 2014 (CDT)
 
+
[http://www.readwriteweb.com/archives/6_mobile_malware_predictions_for_2012.php 6 Mobile Malware Trends for 2012]
+
 
+
== Mailinglists ==
+
 
+
* [http://groups.google.com/group/mobilemalware mobile.malware Google Group]
+

Latest revision as of 10:19, 7 May 2014

Should we change

To make the volume group known to the system
vgexport $VOLUMEGROUP

to

To make the volume group known to the system
vgimport $VOLUMEGROUP

?

vgexport makes volume groups unknown to the system, vgimport makes exported volumes known to the system. See also this. You should also remember, that both vgexport/vgimport alter the data on the physical device. I also added "loop" option to the mount command example, since "-o ro" may alter the data in the file system (replay the journal, etc) .FUF (talk) 10:19, 7 May 2014 (CDT)