1 |
I was present for a discussion about which is the most secure OS. I don't |
2 |
remember the forum but the consensus was that the most secure OS is the one |
3 |
you know. Anyone can wreck a system but not everyone has the ability to |
4 |
maintain a system. |
5 |
|
6 |
I'm not arguing that you can run Windows as tight as Linux (no SELinux, |
7 |
tripwire costs $, etc). What I'm saying is if someone doesn't know Windows |
8 |
they'll do more harm than good. (same Linux). |
9 |
|
10 |
You can probably grep through a virus definition db and find an OS field. |
11 |
Probably ClamAV is your best bet here (but any may work). There's also a |
12 |
50+ gig torrent of all known viruses you can look for. You could also |
13 |
figure out how to query vulns for the OS they're on (mitre or NIST) - |
14 |
probably hard. |
15 |
|
16 |
Reversing - as mentioned above, get a hex editor, and use strings. The |
17 |
other option is that it could have debug symbols still. |
18 |
|
19 |
Indicator lights is a piss poor way to see anything about what might be |
20 |
running. It's like looking at the hdd light to see how much your computer |
21 |
is processing. |
22 |
|
23 |
Ps - the software you're talking about is Windows. |
24 |
On Jul 6, 2013 5:22 AM, "Mick" <michaelkintzios@×××××.com> wrote: |
25 |
|
26 |
> On Saturday 06 Jul 2013 07:57:38 the wrote: |
27 |
> > On 07/06/13 02:21, Dale wrote: |
28 |
> > > William Kenworthy wrote: |
29 |
> > >> On 06/07/13 04:12, Dale wrote: |
30 |
> |
31 |
> > >>> While we was |
32 |
> > >>> chatting, he said that Linux is just as prone to getting a virus as |
33 |
> > >>> windoze and so is a Mac. I think my laughing let him know I wasn't |
34 |
> > >>> buying his comment. |
35 |
> |
36 |
> Well this is just FUD. Linux and BSDs are much much less prone to virus |
37 |
> infection due to their architecture and default authentication |
38 |
> restrictions. |
39 |
> Also your average Linux user, well at least your average Linux desktop |
40 |
> user is |
41 |
> more clued up than the MSWindows equivalent. With the advent of Linux to |
42 |
> mobile devices (Android) this statement is no longer true. |
43 |
> |
44 |
> |
45 |
> > >> food for thought - some years back a member of the local lug picked up |
46 |
> > >> that something was listening on a port that he didn't think should be |
47 |
> in |
48 |
> > >> use. Turned out to be an infected windows binary running under wine |
49 |
> ... |
50 |
> > >> |
51 |
> > >> I presume he had been using wine and this was left running, rather |
52 |
> than |
53 |
> > >> self starting. |
54 |
> > >> |
55 |
> > >> BillK |
56 |
> > > |
57 |
> > > Well, no Wine here. So that won't happen. Actually, I don't have a |
58 |
> > > copy of windoze here at all. Neither of my two rigs have ever had |
59 |
> > > windoze installed on them at all. |
60 |
> |
61 |
> I'm sure some poster in 2003/04 posted in this same list about a MSWindows |
62 |
> malware running in Wine. That's indication of good code as far as I'm |
63 |
> concerned, because most MSWindows programs that I tried would fall over |
64 |
> themselves in Wine! LOL! |
65 |
> |
66 |
> |
67 |
> > > BTW, I have been known to open those attachments before. I usually open |
68 |
> > > them with kwrite or something and try to see what is human readable in |
69 |
> > > there. Most is machine language but there is usually a small portion |
70 |
> > > that is human readable. They sent it and I'm nosy that way. lol |
71 |
> > |
72 |
> > Perhaps it's easier to use strings? |
73 |
> |
74 |
> hexdump -C <suspect_payload> |
75 |
> |
76 |
> You may have to unzip it first, because a lot of malware is zipped to |
77 |
> escape |
78 |
> detection from some simpler anti-virus checkers. You can also use dd and |
79 |
> pipe |
80 |
> it to an antivirus to see if it finds anything known. |
81 |
> |
82 |
> All OS are susceptible to malware, but not all malware are viruses. At |
83 |
> least |
84 |
> one virus has existed for Linux (in the 90s or early 00s), but it was |
85 |
> patched |
86 |
> overnight if I remember right. Other than that I don't know of any |
87 |
> programs |
88 |
> which can be replicated on Linux machines. I think this is because despite |
89 |
> Lennart's efforts no two linux OS are exactly the same. So, as the virus |
90 |
> is |
91 |
> trying to replicate itself it will fall down at the next box it tries to |
92 |
> infect. |
93 |
> |
94 |
> However, rogue add-ons in browsers, increasingly sophisticated JavaScripts, |
95 |
> and HTML 5 with all its cross-domain/cross-site-request potential could |
96 |
> wreck |
97 |
> at least some of your data and steal your information, just as easily as |
98 |
> the |
99 |
> adjacent MSWindows box. Oh, before I forget, did I mention Java? |
100 |
> |
101 |
> Linux running on mobile devices is a different category because there is |
102 |
> great |
103 |
> uniformity of the OS across devices. This is a big target for any malware |
104 |
> writers and state actors who value their coding time: |
105 |
> |
106 |
> http://techcrunch.com/2013/07/04/android-security-hole/ |
107 |
> |
108 |
> -- |
109 |
> Regards, |
110 |
> Mick |
111 |
> |