Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > uk.comp.sys.mac > #180205 > unrolled thread
| Started by | David <BD@invalid.email> |
|---|---|
| First post | 2025-02-16 10:25 +0000 |
| Last post | 2025-02-26 22:46 +0000 |
| Articles | 20 on this page of 138 — 14 participants |
Back to article view | Back to uk.comp.sys.mac
So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 10:25 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-16 06:34 -0500
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 13:45 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-16 06:46 -0700
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-16 10:37 -0500
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 17:26 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-16 14:55 -0500
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 20:44 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 20:46 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 20:55 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 21:07 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 21:16 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 21:17 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 21:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 22:08 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:34 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 23:38 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:54 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 00:21 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 01:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 01:45 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 01:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 01:45 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 04:41 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 05:22 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:53 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 15:33 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 17:17 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 18:00 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 18:17 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 18:22 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 18:59 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 19:19 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 19:36 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 19:52 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 20:49 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 20:56 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 21:20 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 21:23 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:45 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 23:52 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:58 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 00:18 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 12:34 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 14:11 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 14:21 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-26 07:37 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 16:47 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 16:11 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 16:44 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 16:51 +0000
Re: So ...... is this real, or imagined? John <Man@the.keyboard> - 2025-02-17 00:26 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-03-08 08:48 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 01:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 01:41 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 04:41 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 05:25 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 05:42 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:43 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-16 14:57 -0500
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 20:51 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 21:13 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 21:19 +0000
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:25 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-16 23:38 +0000
Re: So ...... is this real, or imagined? Kelly Phillips <KFile@podcasts.org> - 2025-02-16 16:19 -0600
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-16 23:49 +0000
Re: So ...... is this real, or imagined? Kelly Phillips <KFile@podcasts.org> - 2025-02-17 15:58 -0600
Re: So ...... is this real, or imagined? David <BD@invalid.email> - 2025-02-17 22:27 +0000
Re: So ...... is this real, or imagined? Mike Easter <MikeE@ster.invalid> - 2025-02-17 15:08 -0800
Re: So ...... is this real, or imagined? T i m <eternal@spaced.me.uk> - 2025-02-19 23:10 +0000
Re: So ...... is this real, or imagined? David <David@home.today> - 2025-02-19 23:29 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:50 +0000
Re: So ...... is this real, or imagined? David <David@home.today> - 2025-02-22 22:36 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-22 15:42 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 22:42 +0000
Re: So ...... is this real, or imagined? David <David@home.today> - 2025-02-23 00:03 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-23 02:22 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-03-08 08:52 +0000
Re: So ...... is this real, or imagined? Snit <Brock.McNuggets@gmail.com> - 2025-03-08 14:16 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-03-08 22:33 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-03-08 23:19 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:39 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 23:30 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-17 17:11 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-18 00:18 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-17 17:25 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-18 00:58 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-17 18:51 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-18 01:55 +0000
Re: So ...... is this real, or imagined? % <pursent100@gmail.com> - 2025-02-17 19:01 -0700
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-18 02:41 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:38 +0000
Re: So ...... is this real, or imagined? David <David@home.today> - 2025-02-22 22:42 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 23:08 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:46 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 01:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 01:43 +0000
Re: So ...... is this real, or imagined? pothead <pothead@snakebite.com> - 2025-02-17 15:07 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 01:26 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 01:45 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-17 04:41 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-17 05:21 +0000
Re: So ...... is this real, or imagined? Gremlin <nobody@haph.org> - 2025-02-22 05:27 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-22 05:54 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 08:45 +0000
Re: So ...... is this real, or imagined? Jörg Lorenz <hugybear@gmx.net> - 2025-02-26 10:28 +0100
Re: So ...... is this real, or imagined? T i m <eternal@spaced.me.uk> - 2025-03-04 10:11 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-26 04:52 -0500
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 12:46 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-26 08:04 -0500
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 13:57 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 14:01 +0000
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-26 09:47 -0500
Re: So ...... is this real, or imagined? FromTheRafters <FTR@nomail.afraid.org> - 2025-02-26 09:49 -0500
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 15:24 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 15:05 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 16:08 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 16:42 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 16:51 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 16:56 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 17:11 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 17:30 +0000
Re: So ...... is this real, or imagined? Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-02-26 19:36 +0000
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 19:57 +0000
Re: So ...... is this real, or imagined? Jörg Lorenz <hugybear@gmx.net> - 2025-02-26 08:35 +0100
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 08:36 +0000
Re: So ...... is this real, or imagined? Jörg Lorenz <hugybear@gmx.net> - 2025-02-26 11:41 +0100
Re: So ...... is this real, or imagined? David <David.is@home.today> - 2025-02-26 14:02 +0000
Ping: Apd David <David.is@home.today> - 2025-02-26 22:44 +0000
Ping: Apd David <David.is@home.today> - 2025-02-26 22:46 +0000
Page 5 of 7 — ← Prev page 1 2 3 4 [5] 6 7 Next page →
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-23 02:22 +0000 |
| Message-ID | <67ba865b$12$2754$882e4bbb@reader.netnews.com> |
| In reply to | #180431 |
On Feb 22, 2025 at 5:03:30 PM MST, "David" wrote <m1v6uiFkdllU2@mid.individual.net>: > On 22/02/2025 22:42, Brock McNuggets wrote: > [....] >> Gremlin is, as he does, lying his ass off. Look at the recent coding Apd is >> doing... with Carroll. THEY are showing skills. I see that even in quotes. >> Gremlin has shown NO code I have seen on that. Nor on other challenges. He >> posts code that might or might not even be his. I do not care. > > You need to search out a poster called Pooh (the cat) - try the Freeware > Usenet group. He might not admit, though, that Dustin Cook ran rings > around him a few years ago. I am not saying he has no skills... I just do not care what his skills are. I do appreciate when people SHOW skills. And clearly he makes a LOT of things up. > > A start! > https://groups.google.com/g/alt.comp.freeware/c/eMHVPa5AqWo/m/0Q65fT6oBQAJ Looking briefly I do not see Gremlin's posts. I do not pay much attention to what people say of others. I know many are pulled in by arrogance and such... Trump has a of that. He is an authoritarian fascist oligarch and a puppet but he has a cult following in the US. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | David <David.is@home.today> |
|---|---|
| Date | 2025-03-08 08:52 +0000 |
| Message-ID | <m32epjFu6scU2@mid.individual.net> |
| In reply to | #180433 |
On 23/02/2025 02:22, Brock McNuggets wrote: [....] > I do not pay much attention to what people say of others. I know many are > pulled in by arrogance and such... Trump has a of that. He is an authoritarian > fascist oligarch and a puppet but he has a cult following in the US. Over the last couple of weeks he's shown the whole world that he is a bully-boy. :-(
[toc] | [prev] | [next] | [standalone]
| From | Snit <Brock.McNuggets@gmail.com> |
|---|---|
| Date | 2025-03-08 14:16 +0000 |
| Message-ID | <67cc5147$0$21$882e4bbb@reader.netnews.com> |
| In reply to | #180609 |
David <David.is@home.today> wrote: > On 23/02/2025 02:22, Brock McNuggets wrote: > [....] >> I do not pay much attention to what people say of others. I know many are >> pulled in by arrogance and such... Trump has a of that. He is an authoritarian >> fascist oligarch and a puppet but he has a cult following in the US. > > Over the last couple of weeks he's shown the whole world that he is a > bully-boy. :-( > He’s shown us for years — but he’s getting worse. It is good to see some of his past supporters start to see the light. Just hope it’s not too late. You’re not in the US. The situation here is appalling. Thousands being fired and then some begged to be rehired, lies about how that promotes “efficiency” when the firings are tied to investigations into Musk and other leaches on our economy, reduced safety standards and a crumbling stock market. It really does seem Trump has been bought by Putin and Musk. -- Personal attacks from those who troll show their own insecurity. They cannot use reason to show the message to be wrong so they try to feel somehow superior by attacking the messenger. They cling to their attacks and ignore the message time and time again.
[toc] | [prev] | [next] | [standalone]
| From | David <David.is@home.today> |
|---|---|
| Date | 2025-03-08 22:33 +0000 |
| Message-ID | <m33uuiF6ogsU1@mid.individual.net> |
| In reply to | #180610 |
On 08/03/2025 14:16, Snit wrote: > David <David.is@home.today> wrote: >> On 23/02/2025 02:22, Brock McNuggets wrote: >> [....] >>> I do not pay much attention to what people say of others. I know many are >>> pulled in by arrogance and such... Trump has a of that. He is an authoritarian >>> fascist oligarch and a puppet but he has a cult following in the US. >> >> Over the last couple of weeks he's shown the whole world that he is a >> bully-boy. :-( >> > > He’s shown us for years — but he’s getting worse. > > It is good to see some of his past supporters start to see the light. Just > hope it’s not too late. You’re not in the US. The situation here is > appalling. Thousands being fired and then some begged to be rehired, lies > about how that promotes “efficiency” when the firings are tied to > investigations into Musk and other leaches on our economy, reduced safety > standards and a crumbling stock market. > > It really does seem Trump has been bought by Putin and Musk. Might it end up with civil war in the USA?
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-03-08 23:19 +0000 |
| Message-ID | <67ccd074$9$22$882e4bbb@reader.netnews.com> |
| In reply to | #180612 |
On Mar 8, 2025 at 3:33:54 PM MST, "David" wrote <m33uuiF6ogsU1@mid.individual.net>: > On 08/03/2025 14:16, Snit wrote: >> David <David.is@home.today> wrote: >>> On 23/02/2025 02:22, Brock McNuggets wrote: >>> [....] >>>> I do not pay much attention to what people say of others. I know many are >>>> pulled in by arrogance and such... Trump has a of that. He is an authoritarian >>>> fascist oligarch and a puppet but he has a cult following in the US. >>> >>> Over the last couple of weeks he's shown the whole world that he is a >>> bully-boy. :-( >>> >> >> He’s shown us for years — but he’s getting worse. >> >> It is good to see some of his past supporters start to see the light. Just >> hope it’s not too late. You’re not in the US. The situation here is >> appalling. Thousands being fired and then some begged to be rehired, lies >> about how that promotes “efficiency” when the firings are tied to >> investigations into Musk and other leaches on our economy, reduced safety >> standards and a crumbling stock market. >> >> It really does seem Trump has been bought by Putin and Musk. > > Might it end up with civil war in the USA? I think that is a chance, but more likely is that Russia and China will gain power and push wars elsewhere that will grow to include more and more of the world. This could lead to WWW III, which with modern weapons would be VERY bad. At the very least it is almost surely going to lead to world wide economic and political instability. The US will lose power and respect on the world stage. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | Gremlin <nobody@haph.org> |
|---|---|
| Date | 2025-02-22 05:27 +0000 |
| Message-ID | <XnsB28E499E99DDHT1@cF04o3ON7k2lx05.lLC.9r5> |
| In reply to | #180371 |
T i m <eternal@spaced.me.uk> news:vp5od6$2fooh$2@dont-email.me Wed, 19 Feb 2025 23:10:29 GMT in alt.computer.workshop, wrote: > On 17/02/2025 23:08, Mike Easter wrote: >> BDB wrote: >>> Malware *CAN* reside in places other than the main hard drive. Here >>> are a few examples: >> >> In your world, there's a lot more 'magic' in your digital devices than >> need be. >> >> If your 'perception' is that what you 'see' is smoke and mirrors, it >> must be pretty scary and/or confusing. >> > > He is probably 'shell shocked' from when someone dropped a bowl behind > him when he was peeling potatoes in the RN and why he is petrified of > everything. Tim, You really shouldn't try to join in with the intention of mocking or otherwise belittling him as you're trying to do. Last time I checked, you couldn't figure out a text based configuration file on your own. And what little scripting was needed, wasn't done by you. You needed your hand held like a small child to program your own system. Yet you claimed you could read a data sheet for a specific component, understand everything on the datasheet, but 'coding' was beyond you. My total bullshit meter pegged the fuck out. You could have done the work yourself, but, you choose not to. You chose to blame it on some learning issue. The issue is your fucking lazy and refuse to do it yourself. You *could* do it, you just don't want too. I'm surprised Apd has been willing to hold your hand for as long as he has. Nice touch btw trying to recruit him, even offering hardware so he could do it for you more efficiently as well as custom code things your local friends requested; or online forum for it. I don't specifically remember if the additional people seeking help were people you knew in irl or 'forum friends'. I do remember Apd telling you he wasn't interested in doing that, and, I remember you offering to send him a rig so he could do it for you without tying up his hardware. I found your comments concerning my ability to provide assistance very amusing. Apd and FTR (FTR's comment was a fucking riot, and it was clear that you didn't get it) both told you I'm also more than capable of assisting you. Like Snit though, you try the 'I'm just going by what you've shown'. As with Snit, you cherry pick the responses you like and openly disagree with them concerning the ones you don't. You both accept what they tell you, until specifically they mention me. Then, as if by magic, there word has less value. It's funny you think I'm the only one here who's noticed this about you, Tim. FWIW, I still think your a nutless coward. I consider you to be the same as Snit. > "If you finish that lot by the end of your shift we will give you a ride > in an aeroplane". As I said, those who live in glass houses probably shouldn't be throwing stones. I hope this sentence is dumbed down enough for you to comprehend, as I'm sure you and Snit will have trouble parsing my long reply; Mostly due to you both having the attention span of a fucking squirrel. -- I don't need no Dr. All I need...is my lawyer.
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-22 05:39 +0000 |
| Message-ID | <67b962fa$21$2786$882e4bbb@reader.netnews.com> |
| In reply to | #180403 |
On Feb 21, 2025 at 10:27:08 PM MST, "Gremlin" wrote <XnsB28E499E99DDHT1@cF04o3ON7k2lx05.lLC.9r5>: > T i m <eternal@spaced.me.uk> news:vp5od6$2fooh$2@dont-email.me Wed, 19 Feb > 2025 23:10:29 GMT in alt.computer.workshop, wrote: > >> On 17/02/2025 23:08, Mike Easter wrote: >>> BDB wrote: >>>> Malware *CAN* reside in places other than the main hard drive. Here >>>> are a few examples: >>> >>> In your world, there's a lot more 'magic' in your digital devices than >>> need be. >>> >>> If your 'perception' is that what you 'see' is smoke and mirrors, it >>> must be pretty scary and/or confusing. >>> >> >> He is probably 'shell shocked' from when someone dropped a bowl behind >> him when he was peeling potatoes in the RN and why he is petrified of >> everything. > > Tim, > > You really shouldn't try to join in with the intention of mocking or > otherwise belittling him as you're trying to do. Last time I checked, you > couldn't figure out a text based configuration file on your own. And what > little scripting was needed, wasn't done by you. You needed your hand held > like a small child to program your own system. Yet you claimed you could > read a data sheet for a specific component, understand everything on the > datasheet, but 'coding' was beyond you. My total bullshit meter pegged the > fuck out. > > You could have done the work yourself, but, you choose not to. You chose > to blame it on some learning issue. The issue is your fucking lazy and > refuse to do it yourself. You *could* do it, you just don't want too. I'm > surprised Apd has been willing to hold your hand for as long as he has. > Nice touch btw trying to recruit him, even offering hardware so he could > do it for you more efficiently as well as custom code things your local > friends requested; or online forum for it. I don't specifically remember > if the additional people seeking help were people you knew in irl or > 'forum friends'. I do remember Apd telling you he wasn't interested in > doing that, and, I remember you offering to send him a rig so he could do > it for you without tying up his hardware. > > I found your comments concerning my ability to provide assistance very > amusing. Apd and FTR (FTR's comment was a fucking riot, and it was clear > that you didn't get it) both told you I'm also more than capable of > assisting you. Like Snit though, you try the 'I'm just going by what > you've shown'. As with Snit, you cherry pick the responses you like and > openly disagree with them concerning the ones you don't. > You both accept what they tell you, until specifically they mention me. > Then, as if by magic, there word has less value. It's funny you think I'm > the only one here who's noticed this about you, Tim. > > FWIW, I still think your a nutless coward. I consider you to be the same > as Snit. > >> "If you finish that lot by the end of your shift we will give you a ride >> in an aeroplane". > > As I said, those who live in glass houses probably shouldn't be throwing > stones. I hope this sentence is dumbed down enough for you to comprehend, > as I'm sure you and Snit will have trouble parsing my long reply; Mostly > due to you both having the attention span of a fucking squirrel. Your message is a masterclass in projection and insecurity. You start by admonishing Tim for mocking someone, only to launch into an unhinged tirade filled with condescension, name-calling, and unwarranted hostility. It’s almost impressive how quickly you abandon your own advice. You clearly fancy yourself an expert, but your tone screams more about your fragile ego than your actual knowledge. You claim Tim is lazy and blame-shifting, yet the only thing evident here is your desperate need to feel superior. You toss around phrases like “hand-holding” and “nutless coward” as if belittling others will elevate you. Spoiler: it doesn’t. Your disdain for those who don’t immediately bow to your supposed expertise is palpable. You’re upset that Tim, and apparently I, don’t view you as the almighty oracle you imagine yourself to be. Instead of providing helpful information or guiding others constructively, you resort to immature insults and baseless assumptions about their capabilities. And speaking of assumptions, your claim that Tim’s learning issues are just an excuse is not only ignorant but downright cruel. Not everyone learns the same way, and the fact that you interpret his struggles as laziness says more about your lack of empathy than his work ethic. Not everyone’s journey to understanding tech is a straight line, and your impatience with that reality only highlights your own shortcomings as a teacher—or, frankly, as a decent human being. You also accuse Tim and I of cherry-picking responses and disregarding your input when others vouch for you. Maybe instead of blaming them, you should ask yourself why people might hesitate to take your advice. Could it be because your advice often comes wrapped in a thick layer of arrogance and scorn? Or perhaps it’s because your credibility is undermined by your behavior and the need to bash others to feel important. If you truly want respect, try earning it through genuine contributions, patience, and a bit of humility. Because right now, the only thing your message accomplishes is showing everyone just how deeply your insecurities run. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-17 23:30 +0000 |
| Message-ID | <67b3c698$0$2759$882e4bbb@reader.netnews.com> |
| In reply to | #180302 |
On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote <m1hrelFjft2U2@mid.individual.net>: > On 17/02/2025 21:58, Kelly Phillips wrote: >> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >> >>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>> >>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>> AND... >>>>> >>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>> erase your hdd and reinstall from scratch. >>>>> >>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>> >>>> But does it REALLY work? Remember when you used to be extremely fearful >>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>> dark area of the drive, only to spring back to life at some time in the >>>> future? >>> >>> I did *NOT* specify *DRIVE* in that regard. >> >> I don't think you have any idea what you've said. It's all good, though. >> >>> I was suggesting that malware can reside elsewhere within the physical >>> machine. >> >> Yes, I saw that, as well. > > Malware *CAN* reside in places other than the main hard drive. Here are > a few examples: > > 1. **USB Drives and External Storage**: Malware can infect USB drives, > external hard drives, and SD cards. When these devices are plugged into > a computer, the malware can execute or copy itself onto the system. > > 2. **Firmware**: Some sophisticated malware targets the firmware of > devices like the BIOS or UEFI (Unified Extensible Firmware Interface). > It can persist through reboots and even OS reinstalls, making it harder > to remove. > > 3. **Network Devices**: Certain malware can be embedded in devices like > routers, network-attached storage (NAS) devices, or printers. These > devices may have weak security and can serve as entry points for the > malware to infect connected computers. > > 4. **RAM**: Some malware operates purely in the system's memory (RAM), > leaving no trace on the hard drive. This type of malware is often more > challenging to detect, as it can vanish after a reboot. > > 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage > services or network shares. Once a device accesses these locations, it > may download or spread the infection to other systems. > > 6. **Bootable Media**: In some cases, malware can reside on bootable > media, such as CDs, DVDs, or even within boot sector code, and can > execute before the operating system even loads. > > These types of malware often require different approaches to detection > and removal since traditional antivirus tools mainly focus on scanning > hard drives. Oh, you think malware only hides in boring old files and shady downloads? Oh no, my friend. If malware were truly devious, it would lurk in places no one would ever suspect… 1. Inside That One Sock That Always Disappears in the Laundry You thought it was eaten by the washing machine? Nope. That sock was recruited by a cybercriminal to store malicious code in a fabric-based botnet. Every missing sock? Part of the same dark web conspiracy. 2. The Unread Terms & Conditions of Every Website Ever Malware hides in the fine print, knowing full well that no one is actually reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant this malware permission to reorganize your desktop icons into an unholy mess.” 3. The Space Between Your Keyboard Keys You ever drop a crumb between your keyboard keys and never find it again? Yeah. It didn’t just fall—it was taken by malware that lives down there. At night, it whispers “click here for free Bitcoin.” 4. That USB Drive You Found in a Parking Lot “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so malicious, even your toaster would get infected if you plugged it in. In fact, the USB drive itself is sentient—and it wants to be plugged in. 5. The Extra 0.01% on Every Battery Percentage Ever notice your phone stays at 100% for a suspiciously long time? Yeah, that’s malware hoarding that last sliver of battery life for itself, using it to mine crypto and play Minesweeper when you’re not looking. 6. In Your Grandma’s Chain Emails If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient malware so old, it runs on MS-DOS but still manages to steal your passwords. 7. The Digital Equivalent of ‘Under the Couch’ Just like lost TV remotes and potato chips, malware hides in the digital void of your hard drive, chilling in unused sectors and occasionally emerging to whisper “your warranty is expired.” 8. Your Smart Fridge’s Ice Dispenser “Why does the ice taste funny?” Because your smart fridge has been hacked and is now sending encrypted spam emails through its crushed ice function. Also, it keeps ordering way too much mayonnaise for no reason. 9. Inside Your Printer’s Ink Cartridges Your printer refuses to work even though there’s plenty of ink left? That’s malware, siphoning off microscopic droplets of ink to fund its underground operation. Every paper jam is just it trying to assert dominance. 10. The “Close” Button on Fake Ads You think you’re escaping, but nope—that fake “X” button is actually a portal to malware town. Clicking it installs a toolbar that won’t go away and starts calling you by your first name, which is unsettling. 11. The Unused ‘Caps Lock’ Key No one ever presses it on purpose. So malware just lives there, rent-free, waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR ELSE in all caps. 12. Your Wi-Fi Router’s Mysterious Extra Guest Network Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? Because malware is now running its own side business selling stolen bandwidth to confused neighbors and pigeons with internet access. 13. In Your Own Reflection on Your Screen That’s not you. That’s malware impersonating you, making you question reality while it quietly drains your PayPal account and makes all your emails end with “Sent from my iPhone” even when you don’t have one. Moral of the story? Malware is everywhere. Even in places you wouldn’t suspect. Stay safe out there, and if your fridge starts demanding ransom payments… just unplug it. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-02-17 17:11 -0700 |
| Message-ID | <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com> |
| In reply to | #180306 |
Brock McNuggets wrote: > On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote > <m1hrelFjft2U2@mid.individual.net>: > >> On 17/02/2025 21:58, Kelly Phillips wrote: >>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>> >>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>> >>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>> AND... >>>>>> >>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>> erase your hdd and reinstall from scratch. >>>>>> >>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>> >>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>> dark area of the drive, only to spring back to life at some time in the >>>>> future? >>>> >>>> I did *NOT* specify *DRIVE* in that regard. >>> >>> I don't think you have any idea what you've said. It's all good, though. >>> >>>> I was suggesting that malware can reside elsewhere within the physical >>>> machine. >>> >>> Yes, I saw that, as well. >> >> Malware *CAN* reside in places other than the main hard drive. Here are >> a few examples: >> >> 1. **USB Drives and External Storage**: Malware can infect USB drives, >> external hard drives, and SD cards. When these devices are plugged into >> a computer, the malware can execute or copy itself onto the system. >> >> 2. **Firmware**: Some sophisticated malware targets the firmware of >> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >> It can persist through reboots and even OS reinstalls, making it harder >> to remove. >> >> 3. **Network Devices**: Certain malware can be embedded in devices like >> routers, network-attached storage (NAS) devices, or printers. These >> devices may have weak security and can serve as entry points for the >> malware to infect connected computers. >> >> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >> leaving no trace on the hard drive. This type of malware is often more >> challenging to detect, as it can vanish after a reboot. >> >> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >> services or network shares. Once a device accesses these locations, it >> may download or spread the infection to other systems. >> >> 6. **Bootable Media**: In some cases, malware can reside on bootable >> media, such as CDs, DVDs, or even within boot sector code, and can >> execute before the operating system even loads. >> >> These types of malware often require different approaches to detection >> and removal since traditional antivirus tools mainly focus on scanning >> hard drives. > > Oh, you think malware only hides in boring old files and shady downloads? Oh > no, my friend. If malware were truly devious, it would lurk in places no one > would ever suspect… > > 1. Inside That One Sock That Always Disappears in the Laundry > > You thought it was eaten by the washing machine? Nope. That sock was recruited > by a cybercriminal to store malicious code in a fabric-based botnet. Every > missing sock? Part of the same dark web conspiracy. > > 2. The Unread Terms & Conditions of Every Website Ever > > Malware hides in the fine print, knowing full well that no one is actually > reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant > this malware permission to reorganize your desktop icons into an unholy mess.” > > 3. The Space Between Your Keyboard Keys > > You ever drop a crumb between your keyboard keys and never find it again? > Yeah. It didn’t just fall—it was taken by malware that lives down there. At > night, it whispers “click here for free Bitcoin.” > > 4. That USB Drive You Found in a Parking Lot > > “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so > malicious, even your toaster would get infected if you plugged it in. In fact, > the USB drive itself is sentient—and it wants to be plugged in. > > 5. The Extra 0.01% on Every Battery Percentage > > Ever notice your phone stays at 100% for a suspiciously long time? Yeah, > that’s malware hoarding that last sliver of battery life for itself, using it > to mine crypto and play Minesweeper when you’re not looking. > > 6. In Your Grandma’s Chain Emails > > If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE > OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient > malware so old, it runs on MS-DOS but still manages to steal your passwords. > > 7. The Digital Equivalent of ‘Under the Couch’ > > Just like lost TV remotes and potato chips, malware hides in the digital void > of your hard drive, chilling in unused sectors and occasionally emerging to > whisper “your warranty is expired.” > > 8. Your Smart Fridge’s Ice Dispenser > > “Why does the ice taste funny?” Because your smart fridge has been hacked and > is now sending encrypted spam emails through its crushed ice function. Also, > it keeps ordering way too much mayonnaise for no reason. > > 9. Inside Your Printer’s Ink Cartridges > > Your printer refuses to work even though there’s plenty of ink left? That’s > malware, siphoning off microscopic droplets of ink to fund its underground > operation. Every paper jam is just it trying to assert dominance. > > 10. The “Close” Button on Fake Ads > > You think you’re escaping, but nope—that fake “X” button is actually a portal > to malware town. Clicking it installs a toolbar that won’t go away and starts > calling you by your first name, which is unsettling. > > 11. The Unused ‘Caps Lock’ Key > > No one ever presses it on purpose. So malware just lives there, rent-free, > waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR > ELSE in all caps. > > 12. Your Wi-Fi Router’s Mysterious Extra Guest Network > > Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? > Because malware is now running its own side business selling stolen bandwidth > to confused neighbors and pigeons with internet access. > > 13. In Your Own Reflection on Your Screen > > That’s not you. That’s malware impersonating you, making you question reality > while it quietly drains your PayPal account and makes all your emails end with > “Sent from my iPhone” even when you don’t have one. > > Moral of the story? Malware is everywhere. Even in places you wouldn’t > suspect. Stay safe out there, and if your fridge starts demanding ransom > payments… just unplug it. > > that's the box on the porch , right
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-18 00:18 +0000 |
| Message-ID | <67b3d1ec$1$16$882e4bbb@reader.netnews.com> |
| In reply to | #180307 |
On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: > Brock McNuggets wrote: >> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >> <m1hrelFjft2U2@mid.individual.net>: >> >>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>> >>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>> >>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>> AND... >>>>>>> >>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>> erase your hdd and reinstall from scratch. >>>>>>> >>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>> >>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>> future? >>>>> >>>>> I did *NOT* specify *DRIVE* in that regard. >>>> >>>> I don't think you have any idea what you've said. It's all good, though. >>>> >>>>> I was suggesting that malware can reside elsewhere within the physical >>>>> machine. >>>> >>>> Yes, I saw that, as well. >>> >>> Malware *CAN* reside in places other than the main hard drive. Here are >>> a few examples: >>> >>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>> external hard drives, and SD cards. When these devices are plugged into >>> a computer, the malware can execute or copy itself onto the system. >>> >>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>> It can persist through reboots and even OS reinstalls, making it harder >>> to remove. >>> >>> 3. **Network Devices**: Certain malware can be embedded in devices like >>> routers, network-attached storage (NAS) devices, or printers. These >>> devices may have weak security and can serve as entry points for the >>> malware to infect connected computers. >>> >>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>> leaving no trace on the hard drive. This type of malware is often more >>> challenging to detect, as it can vanish after a reboot. >>> >>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>> services or network shares. Once a device accesses these locations, it >>> may download or spread the infection to other systems. >>> >>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>> media, such as CDs, DVDs, or even within boot sector code, and can >>> execute before the operating system even loads. >>> >>> These types of malware often require different approaches to detection >>> and removal since traditional antivirus tools mainly focus on scanning >>> hard drives. >> >> Oh, you think malware only hides in boring old files and shady downloads? Oh >> no, my friend. If malware were truly devious, it would lurk in places no one >> would ever suspect… >> >> 1. Inside That One Sock That Always Disappears in the Laundry >> >> You thought it was eaten by the washing machine? Nope. That sock was recruited >> by a cybercriminal to store malicious code in a fabric-based botnet. Every >> missing sock? Part of the same dark web conspiracy. >> >> 2. The Unread Terms & Conditions of Every Website Ever >> >> Malware hides in the fine print, knowing full well that no one is actually >> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >> this malware permission to reorganize your desktop icons into an unholy mess.” >> >> 3. The Space Between Your Keyboard Keys >> >> You ever drop a crumb between your keyboard keys and never find it again? >> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >> night, it whispers “click here for free Bitcoin.” >> >> 4. That USB Drive You Found in a Parking Lot >> >> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >> malicious, even your toaster would get infected if you plugged it in. In fact, >> the USB drive itself is sentient—and it wants to be plugged in. >> >> 5. The Extra 0.01% on Every Battery Percentage >> >> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >> that’s malware hoarding that last sliver of battery life for itself, using it >> to mine crypto and play Minesweeper when you’re not looking. >> >> 6. In Your Grandma’s Chain Emails >> >> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >> malware so old, it runs on MS-DOS but still manages to steal your passwords. >> >> 7. The Digital Equivalent of ‘Under the Couch’ >> >> Just like lost TV remotes and potato chips, malware hides in the digital void >> of your hard drive, chilling in unused sectors and occasionally emerging to >> whisper “your warranty is expired.” >> >> 8. Your Smart Fridge’s Ice Dispenser >> >> “Why does the ice taste funny?” Because your smart fridge has been hacked and >> is now sending encrypted spam emails through its crushed ice function. Also, >> it keeps ordering way too much mayonnaise for no reason. >> >> 9. Inside Your Printer’s Ink Cartridges >> >> Your printer refuses to work even though there’s plenty of ink left? That’s >> malware, siphoning off microscopic droplets of ink to fund its underground >> operation. Every paper jam is just it trying to assert dominance. >> >> 10. The “Close” Button on Fake Ads >> >> You think you’re escaping, but nope—that fake “X” button is actually a portal >> to malware town. Clicking it installs a toolbar that won’t go away and starts >> calling you by your first name, which is unsettling. >> >> 11. The Unused ‘Caps Lock’ Key >> >> No one ever presses it on purpose. So malware just lives there, rent-free, >> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >> ELSE in all caps. >> >> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >> >> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >> Because malware is now running its own side business selling stolen bandwidth >> to confused neighbors and pigeons with internet access. >> >> 13. In Your Own Reflection on Your Screen >> >> That’s not you. That’s malware impersonating you, making you question reality >> while it quietly drains your PayPal account and makes all your emails end with >> “Sent from my iPhone” even when you don’t have one. >> >> Moral of the story? Malware is everywhere. Even in places you wouldn’t >> suspect. Stay safe out there, and if your fridge starts demanding ransom >> payments… just unplug it. >> >> > that's the box on the porch , right Yes. Glad you understand. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-02-17 17:25 -0700 |
| Message-ID | <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com> |
| In reply to | #180309 |
Brock McNuggets wrote: > On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote > <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: > >> Brock McNuggets wrote: >>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>> <m1hrelFjft2U2@mid.individual.net>: >>> >>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>> >>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>> >>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>> AND... >>>>>>>> >>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>> >>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>> >>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>> future? >>>>>> >>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>> >>>>> I don't think you have any idea what you've said. It's all good, though. >>>>> >>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>> machine. >>>>> >>>>> Yes, I saw that, as well. >>>> >>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>> a few examples: >>>> >>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>> external hard drives, and SD cards. When these devices are plugged into >>>> a computer, the malware can execute or copy itself onto the system. >>>> >>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>> It can persist through reboots and even OS reinstalls, making it harder >>>> to remove. >>>> >>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>> routers, network-attached storage (NAS) devices, or printers. These >>>> devices may have weak security and can serve as entry points for the >>>> malware to infect connected computers. >>>> >>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>> leaving no trace on the hard drive. This type of malware is often more >>>> challenging to detect, as it can vanish after a reboot. >>>> >>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>> services or network shares. Once a device accesses these locations, it >>>> may download or spread the infection to other systems. >>>> >>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>> execute before the operating system even loads. >>>> >>>> These types of malware often require different approaches to detection >>>> and removal since traditional antivirus tools mainly focus on scanning >>>> hard drives. >>> >>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>> no, my friend. If malware were truly devious, it would lurk in places no one >>> would ever suspect… >>> >>> 1. Inside That One Sock That Always Disappears in the Laundry >>> >>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>> missing sock? Part of the same dark web conspiracy. >>> >>> 2. The Unread Terms & Conditions of Every Website Ever >>> >>> Malware hides in the fine print, knowing full well that no one is actually >>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>> this malware permission to reorganize your desktop icons into an unholy mess.” >>> >>> 3. The Space Between Your Keyboard Keys >>> >>> You ever drop a crumb between your keyboard keys and never find it again? >>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>> night, it whispers “click here for free Bitcoin.” >>> >>> 4. That USB Drive You Found in a Parking Lot >>> >>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>> malicious, even your toaster would get infected if you plugged it in. In fact, >>> the USB drive itself is sentient—and it wants to be plugged in. >>> >>> 5. The Extra 0.01% on Every Battery Percentage >>> >>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>> that’s malware hoarding that last sliver of battery life for itself, using it >>> to mine crypto and play Minesweeper when you’re not looking. >>> >>> 6. In Your Grandma’s Chain Emails >>> >>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>> >>> 7. The Digital Equivalent of ‘Under the Couch’ >>> >>> Just like lost TV remotes and potato chips, malware hides in the digital void >>> of your hard drive, chilling in unused sectors and occasionally emerging to >>> whisper “your warranty is expired.” >>> >>> 8. Your Smart Fridge’s Ice Dispenser >>> >>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>> is now sending encrypted spam emails through its crushed ice function. Also, >>> it keeps ordering way too much mayonnaise for no reason. >>> >>> 9. Inside Your Printer’s Ink Cartridges >>> >>> Your printer refuses to work even though there’s plenty of ink left? That’s >>> malware, siphoning off microscopic droplets of ink to fund its underground >>> operation. Every paper jam is just it trying to assert dominance. >>> >>> 10. The “Close” Button on Fake Ads >>> >>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>> calling you by your first name, which is unsettling. >>> >>> 11. The Unused ‘Caps Lock’ Key >>> >>> No one ever presses it on purpose. So malware just lives there, rent-free, >>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>> ELSE in all caps. >>> >>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>> >>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>> Because malware is now running its own side business selling stolen bandwidth >>> to confused neighbors and pigeons with internet access. >>> >>> 13. In Your Own Reflection on Your Screen >>> >>> That’s not you. That’s malware impersonating you, making you question reality >>> while it quietly drains your PayPal account and makes all your emails end with >>> “Sent from my iPhone” even when you don’t have one. >>> >>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>> payments… just unplug it. >>> >>> >> that's the box on the porch , right > > Yes. Glad you understand. > its a trick there's no plug
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-18 00:58 +0000 |
| Message-ID | <67b3db26$8$20$882e4bbb@reader.netnews.com> |
| In reply to | #180310 |
On Feb 17, 2025 at 5:25:11 PM MST, "%" wrote <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com>: > Brock McNuggets wrote: >> On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote >> <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: >> >>> Brock McNuggets wrote: >>>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>>> <m1hrelFjft2U2@mid.individual.net>: >>>> >>>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>>> >>>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>>> >>>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>>> AND... >>>>>>>>> >>>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>>> >>>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>>> >>>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>>> future? >>>>>>> >>>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>>> >>>>>> I don't think you have any idea what you've said. It's all good, though. >>>>>> >>>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>>> machine. >>>>>> >>>>>> Yes, I saw that, as well. >>>>> >>>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>>> a few examples: >>>>> >>>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>>> external hard drives, and SD cards. When these devices are plugged into >>>>> a computer, the malware can execute or copy itself onto the system. >>>>> >>>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>>> It can persist through reboots and even OS reinstalls, making it harder >>>>> to remove. >>>>> >>>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>>> routers, network-attached storage (NAS) devices, or printers. These >>>>> devices may have weak security and can serve as entry points for the >>>>> malware to infect connected computers. >>>>> >>>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>>> leaving no trace on the hard drive. This type of malware is often more >>>>> challenging to detect, as it can vanish after a reboot. >>>>> >>>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>>> services or network shares. Once a device accesses these locations, it >>>>> may download or spread the infection to other systems. >>>>> >>>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>>> execute before the operating system even loads. >>>>> >>>>> These types of malware often require different approaches to detection >>>>> and removal since traditional antivirus tools mainly focus on scanning >>>>> hard drives. >>>> >>>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>>> no, my friend. If malware were truly devious, it would lurk in places no one >>>> would ever suspect… >>>> >>>> 1. Inside That One Sock That Always Disappears in the Laundry >>>> >>>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>>> missing sock? Part of the same dark web conspiracy. >>>> >>>> 2. The Unread Terms & Conditions of Every Website Ever >>>> >>>> Malware hides in the fine print, knowing full well that no one is actually >>>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>>> this malware permission to reorganize your desktop icons into an unholy mess.” >>>> >>>> 3. The Space Between Your Keyboard Keys >>>> >>>> You ever drop a crumb between your keyboard keys and never find it again? >>>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>>> night, it whispers “click here for free Bitcoin.” >>>> >>>> 4. That USB Drive You Found in a Parking Lot >>>> >>>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>>> malicious, even your toaster would get infected if you plugged it in. In fact, >>>> the USB drive itself is sentient—and it wants to be plugged in. >>>> >>>> 5. The Extra 0.01% on Every Battery Percentage >>>> >>>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>>> that’s malware hoarding that last sliver of battery life for itself, using it >>>> to mine crypto and play Minesweeper when you’re not looking. >>>> >>>> 6. In Your Grandma’s Chain Emails >>>> >>>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>>> >>>> 7. The Digital Equivalent of ‘Under the Couch’ >>>> >>>> Just like lost TV remotes and potato chips, malware hides in the digital void >>>> of your hard drive, chilling in unused sectors and occasionally emerging to >>>> whisper “your warranty is expired.” >>>> >>>> 8. Your Smart Fridge’s Ice Dispenser >>>> >>>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>>> is now sending encrypted spam emails through its crushed ice function. Also, >>>> it keeps ordering way too much mayonnaise for no reason. >>>> >>>> 9. Inside Your Printer’s Ink Cartridges >>>> >>>> Your printer refuses to work even though there’s plenty of ink left? That’s >>>> malware, siphoning off microscopic droplets of ink to fund its underground >>>> operation. Every paper jam is just it trying to assert dominance. >>>> >>>> 10. The “Close” Button on Fake Ads >>>> >>>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>>> calling you by your first name, which is unsettling. >>>> >>>> 11. The Unused ‘Caps Lock’ Key >>>> >>>> No one ever presses it on purpose. So malware just lives there, rent-free, >>>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>>> ELSE in all caps. >>>> >>>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>>> >>>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>>> Because malware is now running its own side business selling stolen bandwidth >>>> to confused neighbors and pigeons with internet access. >>>> >>>> 13. In Your Own Reflection on Your Screen >>>> >>>> That’s not you. That’s malware impersonating you, making you question reality >>>> while it quietly drains your PayPal account and makes all your emails end with >>>> “Sent from my iPhone” even when you don’t have one. >>>> >>>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>>> payments… just unplug it. >>>> >>>> >>> that's the box on the porch , right >> >> Yes. Glad you understand. >> > its a trick there's no plug I live on a street that says no outlets anyway. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-02-17 18:51 -0700 |
| Message-ID | <CO2cnY0gSfM5ei76nZ2dnZfqn_QAAAAA@giganews.com> |
| In reply to | #180312 |
Brock McNuggets wrote: > On Feb 17, 2025 at 5:25:11 PM MST, "%" wrote > <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com>: > >> Brock McNuggets wrote: >>> On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote >>> <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: >>> >>>> Brock McNuggets wrote: >>>>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>>>> <m1hrelFjft2U2@mid.individual.net>: >>>>> >>>>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>>>> >>>>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>>>> >>>>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>>>> AND... >>>>>>>>>> >>>>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>>>> >>>>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>>>> >>>>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>>>> future? >>>>>>>> >>>>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>>>> >>>>>>> I don't think you have any idea what you've said. It's all good, though. >>>>>>> >>>>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>>>> machine. >>>>>>> >>>>>>> Yes, I saw that, as well. >>>>>> >>>>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>>>> a few examples: >>>>>> >>>>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>>>> external hard drives, and SD cards. When these devices are plugged into >>>>>> a computer, the malware can execute or copy itself onto the system. >>>>>> >>>>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>>>> It can persist through reboots and even OS reinstalls, making it harder >>>>>> to remove. >>>>>> >>>>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>>>> routers, network-attached storage (NAS) devices, or printers. These >>>>>> devices may have weak security and can serve as entry points for the >>>>>> malware to infect connected computers. >>>>>> >>>>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>>>> leaving no trace on the hard drive. This type of malware is often more >>>>>> challenging to detect, as it can vanish after a reboot. >>>>>> >>>>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>>>> services or network shares. Once a device accesses these locations, it >>>>>> may download or spread the infection to other systems. >>>>>> >>>>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>>>> execute before the operating system even loads. >>>>>> >>>>>> These types of malware often require different approaches to detection >>>>>> and removal since traditional antivirus tools mainly focus on scanning >>>>>> hard drives. >>>>> >>>>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>>>> no, my friend. If malware were truly devious, it would lurk in places no one >>>>> would ever suspect… >>>>> >>>>> 1. Inside That One Sock That Always Disappears in the Laundry >>>>> >>>>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>>>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>>>> missing sock? Part of the same dark web conspiracy. >>>>> >>>>> 2. The Unread Terms & Conditions of Every Website Ever >>>>> >>>>> Malware hides in the fine print, knowing full well that no one is actually >>>>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>>>> this malware permission to reorganize your desktop icons into an unholy mess.” >>>>> >>>>> 3. The Space Between Your Keyboard Keys >>>>> >>>>> You ever drop a crumb between your keyboard keys and never find it again? >>>>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>>>> night, it whispers “click here for free Bitcoin.” >>>>> >>>>> 4. That USB Drive You Found in a Parking Lot >>>>> >>>>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>>>> malicious, even your toaster would get infected if you plugged it in. In fact, >>>>> the USB drive itself is sentient—and it wants to be plugged in. >>>>> >>>>> 5. The Extra 0.01% on Every Battery Percentage >>>>> >>>>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>>>> that’s malware hoarding that last sliver of battery life for itself, using it >>>>> to mine crypto and play Minesweeper when you’re not looking. >>>>> >>>>> 6. In Your Grandma’s Chain Emails >>>>> >>>>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>>>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>>>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>>>> >>>>> 7. The Digital Equivalent of ‘Under the Couch’ >>>>> >>>>> Just like lost TV remotes and potato chips, malware hides in the digital void >>>>> of your hard drive, chilling in unused sectors and occasionally emerging to >>>>> whisper “your warranty is expired.” >>>>> >>>>> 8. Your Smart Fridge’s Ice Dispenser >>>>> >>>>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>>>> is now sending encrypted spam emails through its crushed ice function. Also, >>>>> it keeps ordering way too much mayonnaise for no reason. >>>>> >>>>> 9. Inside Your Printer’s Ink Cartridges >>>>> >>>>> Your printer refuses to work even though there’s plenty of ink left? That’s >>>>> malware, siphoning off microscopic droplets of ink to fund its underground >>>>> operation. Every paper jam is just it trying to assert dominance. >>>>> >>>>> 10. The “Close” Button on Fake Ads >>>>> >>>>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>>>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>>>> calling you by your first name, which is unsettling. >>>>> >>>>> 11. The Unused ‘Caps Lock’ Key >>>>> >>>>> No one ever presses it on purpose. So malware just lives there, rent-free, >>>>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>>>> ELSE in all caps. >>>>> >>>>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>>>> >>>>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>>>> Because malware is now running its own side business selling stolen bandwidth >>>>> to confused neighbors and pigeons with internet access. >>>>> >>>>> 13. In Your Own Reflection on Your Screen >>>>> >>>>> That’s not you. That’s malware impersonating you, making you question reality >>>>> while it quietly drains your PayPal account and makes all your emails end with >>>>> “Sent from my iPhone” even when you don’t have one. >>>>> >>>>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>>>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>>>> payments… just unplug it. >>>>> >>>>> >>>> that's the box on the porch , right >>> >>> Yes. Glad you understand. >>> >> its a trick there's no plug > > I live on a street that says no outlets anyway. > i saw where you live on tv a few days ago
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-18 01:55 +0000 |
| Message-ID | <67b3e8a4$16$14$882e4bbb@reader.netnews.com> |
| In reply to | #180313 |
On Feb 17, 2025 at 6:51:31 PM MST, "%" wrote <CO2cnY0gSfM5ei76nZ2dnZfqn_QAAAAA@giganews.com>: > Brock McNuggets wrote: >> On Feb 17, 2025 at 5:25:11 PM MST, "%" wrote >> <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com>: >> >>> Brock McNuggets wrote: >>>> On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote >>>> <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: >>>> >>>>> Brock McNuggets wrote: >>>>>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>>>>> <m1hrelFjft2U2@mid.individual.net>: >>>>>> >>>>>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>>>>> >>>>>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>>>>> >>>>>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>>>>> AND... >>>>>>>>>>> >>>>>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>>>>> >>>>>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>>>>> >>>>>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>>>>> future? >>>>>>>>> >>>>>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>>>>> >>>>>>>> I don't think you have any idea what you've said. It's all good, though. >>>>>>>> >>>>>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>>>>> machine. >>>>>>>> >>>>>>>> Yes, I saw that, as well. >>>>>>> >>>>>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>>>>> a few examples: >>>>>>> >>>>>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>>>>> external hard drives, and SD cards. When these devices are plugged into >>>>>>> a computer, the malware can execute or copy itself onto the system. >>>>>>> >>>>>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>>>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>>>>> It can persist through reboots and even OS reinstalls, making it harder >>>>>>> to remove. >>>>>>> >>>>>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>>>>> routers, network-attached storage (NAS) devices, or printers. These >>>>>>> devices may have weak security and can serve as entry points for the >>>>>>> malware to infect connected computers. >>>>>>> >>>>>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>>>>> leaving no trace on the hard drive. This type of malware is often more >>>>>>> challenging to detect, as it can vanish after a reboot. >>>>>>> >>>>>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>>>>> services or network shares. Once a device accesses these locations, it >>>>>>> may download or spread the infection to other systems. >>>>>>> >>>>>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>>>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>>>>> execute before the operating system even loads. >>>>>>> >>>>>>> These types of malware often require different approaches to detection >>>>>>> and removal since traditional antivirus tools mainly focus on scanning >>>>>>> hard drives. >>>>>> >>>>>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>>>>> no, my friend. If malware were truly devious, it would lurk in places no one >>>>>> would ever suspect… >>>>>> >>>>>> 1. Inside That One Sock That Always Disappears in the Laundry >>>>>> >>>>>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>>>>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>>>>> missing sock? Part of the same dark web conspiracy. >>>>>> >>>>>> 2. The Unread Terms & Conditions of Every Website Ever >>>>>> >>>>>> Malware hides in the fine print, knowing full well that no one is actually >>>>>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>>>>> this malware permission to reorganize your desktop icons into an unholy mess.” >>>>>> >>>>>> 3. The Space Between Your Keyboard Keys >>>>>> >>>>>> You ever drop a crumb between your keyboard keys and never find it again? >>>>>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>>>>> night, it whispers “click here for free Bitcoin.” >>>>>> >>>>>> 4. That USB Drive You Found in a Parking Lot >>>>>> >>>>>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>>>>> malicious, even your toaster would get infected if you plugged it in. In fact, >>>>>> the USB drive itself is sentient—and it wants to be plugged in. >>>>>> >>>>>> 5. The Extra 0.01% on Every Battery Percentage >>>>>> >>>>>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>>>>> that’s malware hoarding that last sliver of battery life for itself, using it >>>>>> to mine crypto and play Minesweeper when you’re not looking. >>>>>> >>>>>> 6. In Your Grandma’s Chain Emails >>>>>> >>>>>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>>>>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>>>>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>>>>> >>>>>> 7. The Digital Equivalent of ‘Under the Couch’ >>>>>> >>>>>> Just like lost TV remotes and potato chips, malware hides in the digital void >>>>>> of your hard drive, chilling in unused sectors and occasionally emerging to >>>>>> whisper “your warranty is expired.” >>>>>> >>>>>> 8. Your Smart Fridge’s Ice Dispenser >>>>>> >>>>>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>>>>> is now sending encrypted spam emails through its crushed ice function. Also, >>>>>> it keeps ordering way too much mayonnaise for no reason. >>>>>> >>>>>> 9. Inside Your Printer’s Ink Cartridges >>>>>> >>>>>> Your printer refuses to work even though there’s plenty of ink left? That’s >>>>>> malware, siphoning off microscopic droplets of ink to fund its underground >>>>>> operation. Every paper jam is just it trying to assert dominance. >>>>>> >>>>>> 10. The “Close” Button on Fake Ads >>>>>> >>>>>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>>>>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>>>>> calling you by your first name, which is unsettling. >>>>>> >>>>>> 11. The Unused ‘Caps Lock’ Key >>>>>> >>>>>> No one ever presses it on purpose. So malware just lives there, rent-free, >>>>>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>>>>> ELSE in all caps. >>>>>> >>>>>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>>>>> >>>>>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>>>>> Because malware is now running its own side business selling stolen bandwidth >>>>>> to confused neighbors and pigeons with internet access. >>>>>> >>>>>> 13. In Your Own Reflection on Your Screen >>>>>> >>>>>> That’s not you. That’s malware impersonating you, making you question reality >>>>>> while it quietly drains your PayPal account and makes all your emails end with >>>>>> “Sent from my iPhone” even when you don’t have one. >>>>>> >>>>>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>>>>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>>>>> payments… just unplug it. >>>>>> >>>>>> >>>>> that's the box on the porch , right >>>> >>>> Yes. Glad you understand. >>>> >>> its a trick there's no plug >> >> I live on a street that says no outlets anyway. >> > i saw where you live on tv a few days ago I live on TV. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-02-17 19:01 -0700 |
| Message-ID | <CbSdnTH5u_5kdC76nZ2dnZfqnPUAAAAA@giganews.com> |
| In reply to | #180314 |
Brock McNuggets wrote: > On Feb 17, 2025 at 6:51:31 PM MST, "%" wrote > <CO2cnY0gSfM5ei76nZ2dnZfqn_QAAAAA@giganews.com>: > >> Brock McNuggets wrote: >>> On Feb 17, 2025 at 5:25:11 PM MST, "%" wrote >>> <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com>: >>> >>>> Brock McNuggets wrote: >>>>> On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote >>>>> <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: >>>>> >>>>>> Brock McNuggets wrote: >>>>>>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>>>>>> <m1hrelFjft2U2@mid.individual.net>: >>>>>>> >>>>>>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>>>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>>>>>> >>>>>>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>>>>>> >>>>>>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>>>>>> AND... >>>>>>>>>>>> >>>>>>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>>>>>> >>>>>>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>>>>>> >>>>>>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>>>>>> future? >>>>>>>>>> >>>>>>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>>>>>> >>>>>>>>> I don't think you have any idea what you've said. It's all good, though. >>>>>>>>> >>>>>>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>>>>>> machine. >>>>>>>>> >>>>>>>>> Yes, I saw that, as well. >>>>>>>> >>>>>>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>>>>>> a few examples: >>>>>>>> >>>>>>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>>>>>> external hard drives, and SD cards. When these devices are plugged into >>>>>>>> a computer, the malware can execute or copy itself onto the system. >>>>>>>> >>>>>>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>>>>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>>>>>> It can persist through reboots and even OS reinstalls, making it harder >>>>>>>> to remove. >>>>>>>> >>>>>>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>>>>>> routers, network-attached storage (NAS) devices, or printers. These >>>>>>>> devices may have weak security and can serve as entry points for the >>>>>>>> malware to infect connected computers. >>>>>>>> >>>>>>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>>>>>> leaving no trace on the hard drive. This type of malware is often more >>>>>>>> challenging to detect, as it can vanish after a reboot. >>>>>>>> >>>>>>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>>>>>> services or network shares. Once a device accesses these locations, it >>>>>>>> may download or spread the infection to other systems. >>>>>>>> >>>>>>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>>>>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>>>>>> execute before the operating system even loads. >>>>>>>> >>>>>>>> These types of malware often require different approaches to detection >>>>>>>> and removal since traditional antivirus tools mainly focus on scanning >>>>>>>> hard drives. >>>>>>> >>>>>>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>>>>>> no, my friend. If malware were truly devious, it would lurk in places no one >>>>>>> would ever suspect… >>>>>>> >>>>>>> 1. Inside That One Sock That Always Disappears in the Laundry >>>>>>> >>>>>>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>>>>>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>>>>>> missing sock? Part of the same dark web conspiracy. >>>>>>> >>>>>>> 2. The Unread Terms & Conditions of Every Website Ever >>>>>>> >>>>>>> Malware hides in the fine print, knowing full well that no one is actually >>>>>>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>>>>>> this malware permission to reorganize your desktop icons into an unholy mess.” >>>>>>> >>>>>>> 3. The Space Between Your Keyboard Keys >>>>>>> >>>>>>> You ever drop a crumb between your keyboard keys and never find it again? >>>>>>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>>>>>> night, it whispers “click here for free Bitcoin.” >>>>>>> >>>>>>> 4. That USB Drive You Found in a Parking Lot >>>>>>> >>>>>>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>>>>>> malicious, even your toaster would get infected if you plugged it in. In fact, >>>>>>> the USB drive itself is sentient—and it wants to be plugged in. >>>>>>> >>>>>>> 5. The Extra 0.01% on Every Battery Percentage >>>>>>> >>>>>>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>>>>>> that’s malware hoarding that last sliver of battery life for itself, using it >>>>>>> to mine crypto and play Minesweeper when you’re not looking. >>>>>>> >>>>>>> 6. In Your Grandma’s Chain Emails >>>>>>> >>>>>>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>>>>>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>>>>>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>>>>>> >>>>>>> 7. The Digital Equivalent of ‘Under the Couch’ >>>>>>> >>>>>>> Just like lost TV remotes and potato chips, malware hides in the digital void >>>>>>> of your hard drive, chilling in unused sectors and occasionally emerging to >>>>>>> whisper “your warranty is expired.” >>>>>>> >>>>>>> 8. Your Smart Fridge’s Ice Dispenser >>>>>>> >>>>>>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>>>>>> is now sending encrypted spam emails through its crushed ice function. Also, >>>>>>> it keeps ordering way too much mayonnaise for no reason. >>>>>>> >>>>>>> 9. Inside Your Printer’s Ink Cartridges >>>>>>> >>>>>>> Your printer refuses to work even though there’s plenty of ink left? That’s >>>>>>> malware, siphoning off microscopic droplets of ink to fund its underground >>>>>>> operation. Every paper jam is just it trying to assert dominance. >>>>>>> >>>>>>> 10. The “Close” Button on Fake Ads >>>>>>> >>>>>>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>>>>>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>>>>>> calling you by your first name, which is unsettling. >>>>>>> >>>>>>> 11. The Unused ‘Caps Lock’ Key >>>>>>> >>>>>>> No one ever presses it on purpose. So malware just lives there, rent-free, >>>>>>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>>>>>> ELSE in all caps. >>>>>>> >>>>>>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>>>>>> >>>>>>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>>>>>> Because malware is now running its own side business selling stolen bandwidth >>>>>>> to confused neighbors and pigeons with internet access. >>>>>>> >>>>>>> 13. In Your Own Reflection on Your Screen >>>>>>> >>>>>>> That’s not you. That’s malware impersonating you, making you question reality >>>>>>> while it quietly drains your PayPal account and makes all your emails end with >>>>>>> “Sent from my iPhone” even when you don’t have one. >>>>>>> >>>>>>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>>>>>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>>>>>> payments… just unplug it. >>>>>>> >>>>>>> >>>>>> that's the box on the porch , right >>>>> >>>>> Yes. Glad you understand. >>>>> >>>> its a trick there's no plug >>> >>> I live on a street that says no outlets anyway. >>> >> i saw where you live on tv a few days ago > > I live on TV. > i waved at you
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-18 02:41 +0000 |
| Message-ID | <67b3f36f$6$22$882e4bbb@reader.netnews.com> |
| In reply to | #180315 |
On Feb 17, 2025 at 7:01:29 PM MST, "%" wrote <CbSdnTH5u_5kdC76nZ2dnZfqnPUAAAAA@giganews.com>: > Brock McNuggets wrote: >> On Feb 17, 2025 at 6:51:31 PM MST, "%" wrote >> <CO2cnY0gSfM5ei76nZ2dnZfqn_QAAAAA@giganews.com>: >> >>> Brock McNuggets wrote: >>>> On Feb 17, 2025 at 5:25:11 PM MST, "%" wrote >>>> <H0OdnRoqqpz6Ti76nZ2dnZfqnPadnZ2d@giganews.com>: >>>> >>>>> Brock McNuggets wrote: >>>>>> On Feb 17, 2025 at 5:11:35 PM MST, "%" wrote >>>>>> <lqOcnWQGh7CqTS76nZ2dnZfqn_idnZ2d@giganews.com>: >>>>>> >>>>>>> Brock McNuggets wrote: >>>>>>>> On Feb 17, 2025 at 3:27:33 PM MST, "David" wrote >>>>>>>> <m1hrelFjft2U2@mid.individual.net>: >>>>>>>> >>>>>>>>> On 17/02/2025 21:58, Kelly Phillips wrote: >>>>>>>>>> On Sun, 16 Feb 2025 23:49:39 +0000, David <BD@invalid.email> wrote: >>>>>>>>>> >>>>>>>>>>> On 16/02/2025 22:19, Kelly Phillips wrote: >>>>>>>>>>>> On Sun, 16 Feb 2025 21:13:27 +0000, David <BD@invalid.email> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> On 16/02/2025 19:44, Mike Easter wrote: >>>>>>>>>>>>>> AND... >>>>>>>>>>>>> >>>>>>>>>>>>>> ... your most frequently used anti-malware tactic is to 'regularly' >>>>>>>>>>>>>> erase your hdd and reinstall from scratch. >>>>>>>>>>>>> >>>>>>>>>>>>> I'm aware that you don't agree with my methodology - but it works! :-D >>>>>>>>>>>> >>>>>>>>>>>> But does it REALLY work? Remember when you used to be extremely fearful >>>>>>>>>>>> that wiping your drive didn't actually wipe every nook and cranny, and >>>>>>>>>>>> that your malware could possibly "lurk" or "hide" (your words) in some >>>>>>>>>>>> dark area of the drive, only to spring back to life at some time in the >>>>>>>>>>>> future? >>>>>>>>>>> >>>>>>>>>>> I did *NOT* specify *DRIVE* in that regard. >>>>>>>>>> >>>>>>>>>> I don't think you have any idea what you've said. It's all good, though. >>>>>>>>>> >>>>>>>>>>> I was suggesting that malware can reside elsewhere within the physical >>>>>>>>>>> machine. >>>>>>>>>> >>>>>>>>>> Yes, I saw that, as well. >>>>>>>>> >>>>>>>>> Malware *CAN* reside in places other than the main hard drive. Here are >>>>>>>>> a few examples: >>>>>>>>> >>>>>>>>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>>>>>>>> external hard drives, and SD cards. When these devices are plugged into >>>>>>>>> a computer, the malware can execute or copy itself onto the system. >>>>>>>>> >>>>>>>>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>>>>>>>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>>>>>>>> It can persist through reboots and even OS reinstalls, making it harder >>>>>>>>> to remove. >>>>>>>>> >>>>>>>>> 3. **Network Devices**: Certain malware can be embedded in devices like >>>>>>>>> routers, network-attached storage (NAS) devices, or printers. These >>>>>>>>> devices may have weak security and can serve as entry points for the >>>>>>>>> malware to infect connected computers. >>>>>>>>> >>>>>>>>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>>>>>>>> leaving no trace on the hard drive. This type of malware is often more >>>>>>>>> challenging to detect, as it can vanish after a reboot. >>>>>>>>> >>>>>>>>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>>>>>>>> services or network shares. Once a device accesses these locations, it >>>>>>>>> may download or spread the infection to other systems. >>>>>>>>> >>>>>>>>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>>>>>>>> media, such as CDs, DVDs, or even within boot sector code, and can >>>>>>>>> execute before the operating system even loads. >>>>>>>>> >>>>>>>>> These types of malware often require different approaches to detection >>>>>>>>> and removal since traditional antivirus tools mainly focus on scanning >>>>>>>>> hard drives. >>>>>>>> >>>>>>>> Oh, you think malware only hides in boring old files and shady downloads? Oh >>>>>>>> no, my friend. If malware were truly devious, it would lurk in places no one >>>>>>>> would ever suspect… >>>>>>>> >>>>>>>> 1. Inside That One Sock That Always Disappears in the Laundry >>>>>>>> >>>>>>>> You thought it was eaten by the washing machine? Nope. That sock was recruited >>>>>>>> by a cybercriminal to store malicious code in a fabric-based botnet. Every >>>>>>>> missing sock? Part of the same dark web conspiracy. >>>>>>>> >>>>>>>> 2. The Unread Terms & Conditions of Every Website Ever >>>>>>>> >>>>>>>> Malware hides in the fine print, knowing full well that no one is actually >>>>>>>> reading it. Clause 47.8b clearly states: “By clicking ‘I agree,’ you grant >>>>>>>> this malware permission to reorganize your desktop icons into an unholy mess.” >>>>>>>> >>>>>>>> 3. The Space Between Your Keyboard Keys >>>>>>>> >>>>>>>> You ever drop a crumb between your keyboard keys and never find it again? >>>>>>>> Yeah. It didn’t just fall—it was taken by malware that lives down there. At >>>>>>>> night, it whispers “click here for free Bitcoin.” >>>>>>>> >>>>>>>> 4. That USB Drive You Found in a Parking Lot >>>>>>>> >>>>>>>> “Oh cool, free USB drive!” WRONG. That thing is stuffed with malware so >>>>>>>> malicious, even your toaster would get infected if you plugged it in. In fact, >>>>>>>> the USB drive itself is sentient—and it wants to be plugged in. >>>>>>>> >>>>>>>> 5. The Extra 0.01% on Every Battery Percentage >>>>>>>> >>>>>>>> Ever notice your phone stays at 100% for a suspiciously long time? Yeah, >>>>>>>> that’s malware hoarding that last sliver of battery life for itself, using it >>>>>>>> to mine crypto and play Minesweeper when you’re not looking. >>>>>>>> >>>>>>>> 6. In Your Grandma’s Chain Emails >>>>>>>> >>>>>>>> If your grandma ever forwarded you an email that said “SEND THIS TO 10 PEOPLE >>>>>>>> OR YOUR DOG WILL LEARN TO TYPE”—congratulations! That email contained ancient >>>>>>>> malware so old, it runs on MS-DOS but still manages to steal your passwords. >>>>>>>> >>>>>>>> 7. The Digital Equivalent of ‘Under the Couch’ >>>>>>>> >>>>>>>> Just like lost TV remotes and potato chips, malware hides in the digital void >>>>>>>> of your hard drive, chilling in unused sectors and occasionally emerging to >>>>>>>> whisper “your warranty is expired.” >>>>>>>> >>>>>>>> 8. Your Smart Fridge’s Ice Dispenser >>>>>>>> >>>>>>>> “Why does the ice taste funny?” Because your smart fridge has been hacked and >>>>>>>> is now sending encrypted spam emails through its crushed ice function. Also, >>>>>>>> it keeps ordering way too much mayonnaise for no reason. >>>>>>>> >>>>>>>> 9. Inside Your Printer’s Ink Cartridges >>>>>>>> >>>>>>>> Your printer refuses to work even though there’s plenty of ink left? That’s >>>>>>>> malware, siphoning off microscopic droplets of ink to fund its underground >>>>>>>> operation. Every paper jam is just it trying to assert dominance. >>>>>>>> >>>>>>>> 10. The “Close” Button on Fake Ads >>>>>>>> >>>>>>>> You think you’re escaping, but nope—that fake “X” button is actually a portal >>>>>>>> to malware town. Clicking it installs a toolbar that won’t go away and starts >>>>>>>> calling you by your first name, which is unsettling. >>>>>>>> >>>>>>>> 11. The Unused ‘Caps Lock’ Key >>>>>>>> >>>>>>>> No one ever presses it on purpose. So malware just lives there, rent-free, >>>>>>>> waiting for the moment you accidentally hit it so it can shout: BUY A VPN OR >>>>>>>> ELSE in all caps. >>>>>>>> >>>>>>>> 12. Your Wi-Fi Router’s Mysterious Extra Guest Network >>>>>>>> >>>>>>>> Why does your Wi-Fi have an extra network called “ClickHereForFreeInternet”? >>>>>>>> Because malware is now running its own side business selling stolen bandwidth >>>>>>>> to confused neighbors and pigeons with internet access. >>>>>>>> >>>>>>>> 13. In Your Own Reflection on Your Screen >>>>>>>> >>>>>>>> That’s not you. That’s malware impersonating you, making you question reality >>>>>>>> while it quietly drains your PayPal account and makes all your emails end with >>>>>>>> “Sent from my iPhone” even when you don’t have one. >>>>>>>> >>>>>>>> Moral of the story? Malware is everywhere. Even in places you wouldn’t >>>>>>>> suspect. Stay safe out there, and if your fridge starts demanding ransom >>>>>>>> payments… just unplug it. >>>>>>>> >>>>>>>> >>>>>>> that's the box on the porch , right >>>>>> >>>>>> Yes. Glad you understand. >>>>>> >>>>> its a trick there's no plug >>>> >>>> I live on a street that says no outlets anyway. >>>> >>> i saw where you live on tv a few days ago >> >> I live on TV. >> > i waved at you That's the microwave. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | Gremlin <nobody@haph.org> |
|---|---|
| Date | 2025-02-22 05:27 +0000 |
| Message-ID | <XnsB28E498F1958HT1@cF04o3ON7k2lx05.lLC.9r5> |
| In reply to | #180302 |
David <BD@invalid.email> news:m1hrelFjft2U2@mid.individual.net Mon, 17 Feb 2025 22:27:33 GMT in alt.computer.workshop, wrote: > Malware *CAN* reside in places other than the main hard drive. Here are > a few examples: I'm sure he's well aware of the methods you shared. You actually duplicated atleast one...You did this because you don't actually understand things concerning these machines on a technical level. For you, some of what can be done with them appears to be black magic or something. At some point, you assumed that some malware cannot be removed; once you have it, you have it it's a done deal. That's not actually true, and I've tried to explain this to you several times. You ignore me though and continue on with it. It is somewhat annoying, but, I've learned to look over it. > 1. **USB Drives and External Storage**: Malware can infect USB drives, > external hard drives, and SD cards. When these devices are plugged into > a computer, the malware can execute or copy itself onto the system. Via auto run exploits if inserted into a windows based rig, otherwise firmware modification; but again, it'll be OS specific. And with Linux, it could even be distro specific. IE: works fine on say Linux Mint, but won't work on MXLinux. They're based on different bases and this does sometimes cause issues. > 2. **Firmware**: Some sophisticated malware targets the firmware of > devices like the BIOS or UEFI (Unified Extensible Firmware Interface). > It can persist through reboots and even OS reinstalls, making it harder > to remove. It doesn't have to be sophisticated to go that route, but, most of the time when they do firmware exploits, it's pretty advanced code with several payloads. That's been my experience anyway. > 3. **Network Devices**: Certain malware can be embedded in devices like > routers, network-attached storage (NAS) devices, or printers. These > devices may have weak security and can serve as entry points for the > malware to infect connected computers. This is one place where you duplicated yourself. It's firmware, bro. Instead of doing a copy/paste, why don't you actually read the material and do what we were taught to do as children? Acquire more details; research the matter so that you have a solid understanding of what's being discussed. We used to use actual books for that, but the internet made that task much easier. You still have to actually do it tho. :) > 4. **RAM**: Some malware operates purely in the system's memory (RAM), > leaving no trace on the hard drive. This type of malware is often more > challenging to detect, as it can vanish after a reboot. It still has to be loaded from a solid point to get into the RAM. And while it's in solid form, if you don't use the host OS, you can hunt it down. All Malware technically resides in RAM anyhow, they're programs like any other. They just do things that they shouldn't be doing. But, at the end of the day they are still programs, and can be treated the same as any other program. It's not possible to make truely undetectable malware David, is the point, i'm trying to make here. It's quite possible to make it very difficult and not possible with certain tools; but as I'm sure you understand, there's more than one kind of tool. > 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage > services or network shares. Once a device accesses these locations, it > may download or spread the infection to other systems. That's a software issue. It's nothing new, and, I'd be hesitant to call that an actual method. > 6. **Bootable Media**: In some cases, malware can reside on bootable > media, such as CDs, DVDs, or even within boot sector code, and can > execute before the operating system even loads. I'm well aware. It was one of the keypoints I raised with snit when he tried his creative routine concerning some of what I wrote about a floppy hanging a machine during boot if the bootsector didn't have pass along to HD based os and transfer control. He conveniently leaves out my followup to my own post where I got specific and asked why he'd allow the machine to even attempt a floppy boot. Initially he claimed he was in charge of those machines, but!, the moment I asked why he'd do that, he was quick to change his tune and reverse course that he wasn't really in charge of them. A boot sector virus is a bit of a pain to write too, because you are very limited on available physical space. If you're a complex critter, you have to store the bulk of your code somewhere else, and load it later on. Or, reconfigure the host to do that for you. You can just remain a tiny boot sector virus and spread your code into other sectors that weren't in use, but to protect your code, you went ahead and marked them as being in use so the host OS wouldn't go and trash you when someone saved or created a file, or did anything else to increase the space consumed. Even a swap file adjustment could wreck your code and screw you good. code wise. > These types of malware often require different approaches to detection > and removal since traditional antivirus tools mainly focus on scanning > hard drives. This article you copy and pasted the contents from has issues, David. And it's flatout wrong concerning the limitations of AV or what they spend the bulk of their time scanning. Scanning for physical copies of malware is only a section of their code. In order to properly write a self replicating program that wasn't going to be tagged right off, you had to know how your adversaries worked; I'm far from the only Vxer at the time who reverse engineered the 'enemies' software. They do it to each other too, btw, they just don't come outright and say that because it's a total violation of various licensing agreements and they could actually be sued over it. AV companies do reverse engineer all software they encounter; malware and legit software alike. They make no distinction other than to do a writeup on the Malware and remain silent on what they learned from reverse engineering their competitors. Multiple companies reverse engineered my BugHunter program too; It's one of the reasons (the most important one imho) I wasn't worried about people thinking it had a logic bomb or micky. If it did, I'd have been exposed by all of the major players and destroy any chance I had of redeeming myself and earning the respect as one of the mostly good guys. I tried to explain this to Snit before, but, snit being snit wouldn't hear a fucking word of it. As you and I both know, even if you choose not to admit it in public, He's not a peer of mine and likely won't ever be. And, this pisses him the fuck off. I'm not the only one who's tech savvy that he's created a problem with. He does it in every technical newsgroup he joins. He singles people like me out. He wants to be seen as a peer on the technical fronts. And, I'm sure he's here because of you. Infact, the initial interaction he had with me concerning 3D printing tech gave it away. Do you remember that? He shared a url to a website that specialized in 3D printers and asked if I could determine what kind of printer tech they were using. They openly shared that information on the home page; I simply pointed that out to him, everybody who visited the site could see the same information as I was viewing. He was trying to talk down to me and do his thing. It didn't work out for him. He's all about trying to bring up an 'ego' these days, doesn't want to discuss points by point basis, just wants to use chatgpt and troll. He's always been a troll mind you, but, he's not even trying to hide it these days. Still lies his fucking ass off, and still tries to project his known reading comprehension issues on me. He can't make the sale though, ffs, he just pulls things entirely from his asshole. I think? I understand why you associate with him, but, David, he's not the one who's going to bring me down. Once again, you've selected someone to help you out that can't stand toe to toe with me. He never could. If you'll recall, when the can we help him with his computer discussion started; I asked him some questions about it when it was running, and then I shared my initial diagnosis; that I don't think we have a mainboard problem, I think we're looking at a bad hard drive. If you'll recall, SC did not initially agree with my assesment. Which is understandable; he didn't know that I'm actually a multi cert comp technician who's built and serviced tens of thousands of machines during the course of my career. I wasn't asking Snit those questions randomly, and I didn't take a shot in the dark guess on my diagnosis for the rig, I was going by decades of hands on experience; actually working on them for a living. Not doing it on the side from my house. I've done that too, on my off days, but I have an actual lab here to do that stuff with. It's basically a duplicate of everything I was able to access at the shop I worked for. My former employer insisted I do this due to my health; some days I just couldn't go in and stay all day, but I could swing by and pickup a few machines to work on, to lighten the shops load. Back then you really needed multiple computers to assist you with repairs. That's especially true today. You could get buy using the only PC you had if you were in a bind, but, it's much more efficient to have multiple machines available to you. You can assign tasks more efficiently that way. Especially with data recovery efforts, that can take hours to days and the machine doing the task is tied up, focused entirely on that single project. It's not wise to try and use said machine while it's in the middle of data recovery. you may not get a 2nd chance to pull data if it's interrupted. And, as you well know, my diagnosis was confirmed as being accurate, despite Snits efforts to stall and take his sweet time, deliberately ignoring my specific instructions and taking 'help' from anyone who posted. That actually makes troubleshooting remotely a bit of a pain. Time is wasted, and it only adds to possible confusion for him. I tried to explain this to you and SC; but you guys refused to just lemme do my thing. I'd have had that confirmed diagnosis a lot sooner if you guys had remained on the sidelines. I understand, you were both trying to help; but when you're actually serious about the trade, you don't do that. It's too many chiefs and too few indians then, you understand? I'm not trying to insult either of you, btw, I'm just reminding you of things. The two of you were basically, I think without even realizing it, helping Snit try to make me look incompetent. That was the actual reason he agreed to let me try and diagnose his machine via usenet; He didn't think I'd actually be able to. He thought I was BSing, just as he thought I wasn't actually Raid for a long time. Until well, enough proof was posted that he couldn't continue making that claim. It just wasn't working out. Now he's trying to sell the story that he never did that. Now he's trying to say I accused him of not posting as Raid or some completely unrelated bullshit; that wasn't what I accused him of. And you know that. I was rightfully accusing him of lieing and spinning things around. Which publically agree or not, you know damn well that's part of what he does here. I do understand why SC disagreed with my initial diagnosis; that's where hands on experience comes into play, in my favor in this case. I've never been what you call a hobbyist level computer user. My experience isn't limited to fixing friends and family computers as time allowed. I actually did it, every day, for a living. I didn't even spend a solid hour doing my CompTIA testing, David. I was high at the time and I fucked around; but I still passed with 95% average. Had I actually dedicated myself to it, I'd have 0wned it outright. I'm not a hobbyist repair person friends and family call; I have considerably more hands on experience from repairing hardware to software. FFS, I've rebuilt a corrupted windows registry hive by hand using a hex editor and writing little tools with ASIC to patch bytes. It took me 3 fucking hours, but I did it. Why didn't I just reload it? Well, that machine ran a plasma cutter that used proprietary as fuck software with a dongle and he had no way to reinstall it; lost the cdrom a long time ago. And despite my efforts to find a suitable copy online that would specifically run that hardware; It was deuces. So, if I couldn't keep the software in working condition, there was no point in going any further with the rig. It would either be able to run that huge plasma cutter or it wouldn't. And if it didn't, we didn't get paid for the job. Boss didn't like non paying jobs very much. It was in my best interest to repair whatever machine came onto my bench. I didn't always have the luxury of rename windows directories and reload, or wipe and reload. Sometimes, the machine had very specific software that required you actually be a real Technician because you'd be doing what had to be done to restore the OS and software, without reloading; because as I wrote above, that wasn't an option. I've always hated that 'fix' methodology too, because if you really know what the fuck you're doing, you should not have to resort to a clean reload. Anybody can wipe and reload a box, you do it all the fucking time. SC probably thought I was getting ahead of myself. But, again, I remind you I asked snit specific questions about the machines behavior and they weren't random ones. I was getting a feel for the status, mostly due to the way in which he described it began to fail on him. My decades of fixing these fucking things for a living is what lead me to that diagnosis. You have to understand, I've been repairing these rigs since before I was even a teenager; that's how I made money as a kid going to school. I didn't grow up, become an adult, and then decide 'hey I wanna work on computers and electronics' I was *already doing that* and had been since I was literally, a little kid. Snit will come along and accuse me of having a huge ego here, I've little doubt. But, I'm sure you know this has fuckall to do with any ego on my part. I'm simply being blunt candid and honest. There's no ego here, I have nothing to prove.. My own known history did that for me. You read what chatgpt actually knows about me, you've even shared some of it's information on me here. I'm not an ego driven maniac that snits working so hard to paint me out as; when he could be more productive and work for a living. If I was, you wouldn't have interacted with me beyond the first couple of emails between us. Snit's just using that as his latest bullshit excuse for his inability to keep up with me. A situation he put himself in, too, btw. I wasn't trying to 'compete' with him or anyone else here. I respect (greatly) two of the posters especially, and you know them both. And you know why I hold them in such high regard too. They are, 100%, peers of mine. We're on the same level for the most part. Perhaps some skillset differences due to personal interest differences, but at the end of the day, they're just as competent as I am. I do not question the advice they provide others here when they choose to do so; I'm sure you've noticed that. I'm also sure you've noticed that when either of them or both disagrees with me, I still remain respectful (er for the most part anyhow. I do have a sailors mouth, after all. And, I really am the same way irl as I am here online. There is no persona, it's just me) I don't try to dog either of them. We can have arguments, etc, and, still not take it personal. As an actual peer would. Sorry for the long response, but, I don't have the free time I once had to fiddle fart and fuck around. So I tend to condense things. Hopefully you're okay with this and we can have reasonable adult conversations. -- I don't need no Dr. All I need...is my lawyer.
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-22 05:38 +0000 |
| Message-ID | <67b962ec$15$2754$882e4bbb@reader.netnews.com> |
| In reply to | #180402 |
On Feb 21, 2025 at 10:27:07 PM MST, "Gremlin" wrote <XnsB28E498F1958HT1@cF04o3ON7k2lx05.lLC.9r5>: > David <BD@invalid.email> news:m1hrelFjft2U2@mid.individual.net Mon, 17 Feb > 2025 22:27:33 GMT in alt.computer.workshop, wrote: > >> Malware *CAN* reside in places other than the main hard drive. Here are >> a few examples: > > I'm sure he's well aware of the methods you shared. You actually duplicated > atleast one...You did this because you don't actually understand things > concerning these machines on a technical level. For you, some of what can be > done with them appears to be black magic or something. At some point, you > assumed that some malware cannot be removed; once you have it, you have it > it's a done deal. That's not actually true, and I've tried to explain this > to you several times. You ignore me though and continue on with it. It is > somewhat annoying, but, I've learned to look over it. > >> 1. **USB Drives and External Storage**: Malware can infect USB drives, >> external hard drives, and SD cards. When these devices are plugged into >> a computer, the malware can execute or copy itself onto the system. > > Via auto run exploits if inserted into a windows based rig, otherwise > firmware modification; but again, it'll be OS specific. And with Linux, it > could even be distro specific. IE: works fine on say Linux Mint, but won't > work on MXLinux. They're based on different bases and this does sometimes > cause issues. > >> 2. **Firmware**: Some sophisticated malware targets the firmware of >> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >> It can persist through reboots and even OS reinstalls, making it harder >> to remove. > > It doesn't have to be sophisticated to go that route, but, most of the time > when they do firmware exploits, it's pretty advanced code with several > payloads. That's been my experience anyway. > >> 3. **Network Devices**: Certain malware can be embedded in devices like >> routers, network-attached storage (NAS) devices, or printers. These >> devices may have weak security and can serve as entry points for the >> malware to infect connected computers. > > This is one place where you duplicated yourself. It's firmware, bro. Instead > of doing a copy/paste, why don't you actually read the material and do what > we were taught to do as children? Acquire more details; research the matter > so that you have a solid understanding of what's being discussed. We used > to use actual books for that, but the internet made that task much easier. > You still have to actually do it tho. :) > >> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >> leaving no trace on the hard drive. This type of malware is often more >> challenging to detect, as it can vanish after a reboot. > > It still has to be loaded from a solid point to get into the RAM. And while > it's in solid form, if you don't use the host OS, you can hunt it down. All > Malware technically resides in RAM anyhow, they're programs like any other. > They just do things that they shouldn't be doing. But, at the end of the day > they are still programs, and can be treated the same as any other program. > > It's not possible to make truely undetectable malware David, is the point, > i'm trying to make here. It's quite possible to make it very difficult and > not possible with certain tools; but as I'm sure you understand, there's > more than one kind of tool. > >> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >> services or network shares. Once a device accesses these locations, it >> may download or spread the infection to other systems. > > That's a software issue. It's nothing new, and, I'd be hesitant to call that > an actual method. > >> 6. **Bootable Media**: In some cases, malware can reside on bootable >> media, such as CDs, DVDs, or even within boot sector code, and can >> execute before the operating system even loads. > > I'm well aware. It was one of the keypoints I raised with snit when he tried > his creative routine concerning some of what I wrote about a floppy hanging > a machine during boot if the bootsector didn't have pass along to HD based > os and transfer control. He conveniently leaves out my followup to my own > post where I got specific and asked why he'd allow the machine to even > attempt a floppy boot. Initially he claimed he was in charge of those > machines, but!, the moment I asked why he'd do that, he was quick to change > his tune and reverse course that he wasn't really in charge of them. > > A boot sector virus is a bit of a pain to write too, because you are very > limited on available physical space. If you're a complex critter, you have > to store the bulk of your code somewhere else, and load it later on. Or, > reconfigure the host to do that for you. You can just remain a tiny boot > sector virus and spread your code into other sectors that weren't in use, > but to protect your code, you went ahead and marked them as being in use so > the host OS wouldn't go and trash you when someone saved or created a file, > or did anything else to increase the space consumed. Even a swap file > adjustment could wreck your code and screw you good. code wise. > >> These types of malware often require different approaches to detection >> and removal since traditional antivirus tools mainly focus on scanning >> hard drives. > > This article you copy and pasted the contents from has issues, David. And > it's flatout wrong concerning the limitations of AV or what they spend the > bulk of their time scanning. Scanning for physical copies of malware is only > a section of their code. In order to properly write a self replicating > program that wasn't going to be tagged right off, you had to know how your > adversaries worked; I'm far from the only Vxer at the time who reverse > engineered the 'enemies' software. They do it to each other too, btw, they > just don't come outright and say that because it's a total violation of > various licensing agreements and they could actually be sued over it. > > AV companies do reverse engineer all software they encounter; malware and > legit software alike. They make no distinction other than to do a writeup on > the Malware and remain silent on what they learned from reverse engineering > their competitors. Multiple companies reverse engineered my BugHunter > program too; It's one of the reasons (the most important one imho) I wasn't > worried about people thinking it had a logic bomb or micky. If it did, I'd > have been exposed by all of the major players and destroy any chance I had > of redeeming myself and earning the respect as one of the mostly good guys. > I tried to explain this to Snit before, but, snit being snit wouldn't hear a > fucking word of it. As you and I both know, even if you choose not to admit > it in public, He's not a peer of mine and likely won't ever be. And, this > pisses him the fuck off. I'm not the only one who's tech savvy that he's > created a problem with. He does it in every technical newsgroup he joins. He > singles people like me out. He wants to be seen as a peer on the technical > fronts. > > And, I'm sure he's here because of you. Infact, the initial interaction he > had with me concerning 3D printing tech gave it away. Do you remember that? > He shared a url to a website that specialized in 3D printers and asked if I > could determine what kind of printer tech they were using. They openly > shared that information on the home page; I simply pointed that out to him, > everybody who visited the site could see the same information as I was > viewing. He was trying to talk down to me and do his thing. It didn't work > out for him. > > He's all about trying to bring up an 'ego' these days, doesn't want to > discuss points by point basis, just wants to use chatgpt and troll. He's > always been a troll mind you, but, he's not even trying to hide it these > days. Still lies his fucking ass off, and still tries to project his known > reading comprehension issues on me. He can't make the sale though, ffs, he > just pulls things entirely from his asshole. > > I think? I understand why you associate with him, but, David, he's not the > one who's going to bring me down. Once again, you've selected someone to > help you out that can't stand toe to toe with me. He never could. If you'll > recall, when the can we help him with his computer discussion started; I > asked him some questions about it when it was running, and then I shared my > initial diagnosis; that I don't think we have a mainboard problem, I think > we're looking at a bad hard drive. If you'll recall, SC did not initially > agree with my assesment. Which is understandable; he didn't know that I'm > actually a multi cert comp technician who's built and serviced tens of > thousands of machines during the course of my career. > > I wasn't asking Snit those questions randomly, and I didn't take a shot in > the dark guess on my diagnosis for the rig, I was going by decades of hands > on experience; actually working on them for a living. Not doing it on the > side from my house. I've done that too, on my off days, but I have an actual > lab here to do that stuff with. It's basically a duplicate of everything I > was able to access at the shop I worked for. My former employer insisted I > do this due to my health; some days I just couldn't go in and stay all day, > but I could swing by and pickup a few machines to work on, to lighten the > shops load. > > Back then you really needed multiple computers to assist you with repairs. > That's especially true today. You could get buy using the only PC you had if > you were in a bind, but, it's much more efficient to have multiple machines > available to you. You can assign tasks more efficiently that way. Especially > with data recovery efforts, that can take hours to days and the machine > doing the task is tied up, focused entirely on that single project. It's not > wise to try and use said machine while it's in the middle of data recovery. > you may not get a 2nd chance to pull data if it's interrupted. > > And, as you well know, my diagnosis was confirmed as being accurate, despite > Snits efforts to stall and take his sweet time, deliberately ignoring my > specific instructions and taking 'help' from anyone who posted. That > actually makes troubleshooting remotely a bit of a pain. Time is wasted, and > it only adds to possible confusion for him. I tried to explain this to you > and SC; but you guys refused to just lemme do my thing. I'd have had that > confirmed diagnosis a lot sooner if you guys had remained on the sidelines. > I understand, you were both trying to help; but when you're actually serious > about the trade, you don't do that. > > It's too many chiefs and too few indians then, you understand? I'm not > trying to insult either of you, btw, I'm just reminding you of things. The > two of you were basically, I think without even realizing it, helping Snit > try to make me look incompetent. That was the actual reason he agreed to let > me try and diagnose his machine via usenet; He didn't think I'd actually be > able to. He thought I was BSing, just as he thought I wasn't actually Raid > for a long time. Until well, enough proof was posted that he couldn't > continue making that claim. It just wasn't working out. Now he's trying to > sell the story that he never did that. Now he's trying to say I accused him > of not posting as Raid or some completely unrelated bullshit; that wasn't > what I accused him of. And you know that. I was rightfully accusing him of > lieing and spinning things around. Which publically agree or not, you know > damn well that's part of what he does here. > > I do understand why SC disagreed with my initial diagnosis; that's where > hands on experience comes into play, in my favor in this case. I've never > been what you call a hobbyist level computer user. My experience isn't > limited to fixing friends and family computers as time allowed. I actually > did it, every day, for a living. I didn't even spend a solid hour doing my > CompTIA testing, David. I was high at the time and I fucked around; but I > still passed with 95% average. Had I actually dedicated myself to it, I'd > have 0wned it outright. I'm not a hobbyist repair person friends and family > call; I have considerably more hands on experience from repairing hardware > to software. FFS, I've rebuilt a corrupted windows registry hive by hand > using a hex editor and writing little tools with ASIC to patch bytes. It > took me 3 fucking hours, but I did it. Why didn't I just reload it? Well, > that machine ran a plasma cutter that used proprietary as fuck software with > a dongle and he had no way to reinstall it; lost the cdrom a long time ago. > And despite my efforts to find a suitable copy online that would > specifically run that hardware; It was deuces. So, if I couldn't keep the > software in working condition, there was no point in going any further with > the rig. It would either be able to run that huge plasma cutter or it > wouldn't. And if it didn't, we didn't get paid for the job. Boss didn't like > non paying jobs very much. It was in my best interest to repair whatever > machine came onto my bench. > > I didn't always have the luxury of rename windows directories and reload, or > wipe and reload. Sometimes, the machine had very specific software that > required you actually be a real Technician because you'd be doing what had > to be done to restore the OS and software, without reloading; because as I > wrote above, that wasn't an option. I've always hated that 'fix' methodology > too, because if you really know what the fuck you're doing, you should not > have to resort to a clean reload. Anybody can wipe and reload a box, you do > it all the fucking time. > > SC probably thought I was getting ahead of myself. But, again, I remind you > I asked snit specific questions about the machines behavior and they weren't > random ones. I was getting a feel for the status, mostly due to the way in > which he described it began to fail on him. My decades of fixing these > fucking things for a living is what lead me to that diagnosis. You have to > understand, I've been repairing these rigs since before I was even a > teenager; that's how I made money as a kid going to school. I didn't grow up, > become an adult, and then decide 'hey I wanna work on computers and > electronics' I was *already doing that* and had been since I was literally, > a little kid. > > Snit will come along and accuse me of having a huge ego here, I've little > doubt. But, I'm sure you know this has fuckall to do with any ego on my part. > I'm simply being blunt candid and honest. There's no ego here, I have > nothing to prove.. My own known history did that for me. You read what > chatgpt actually knows about me, you've even shared some of it's information > on me here. I'm not an ego driven maniac that snits working so hard to paint > me out as; when he could be more productive and work for a living. > > If I was, you wouldn't have interacted with me beyond the first couple of > emails between us. Snit's just using that as his latest bullshit excuse for > his inability to keep up with me. A situation he put himself in, too, btw. I > wasn't trying to 'compete' with him or anyone else here. I respect (greatly) > two of the posters especially, and you know them both. And you know why I > hold them in such high regard too. > > They are, 100%, peers of mine. We're on the same level for the most part. > Perhaps some skillset differences due to personal interest differences, but > at the end of the day, they're just as competent as I am. I do not question > the advice they provide others here when they choose to do so; I'm sure > you've noticed that. I'm also sure you've noticed that when either of them > or both disagrees with me, I still remain respectful (er for the most part > anyhow. I do have a sailors mouth, after all. And, I really am the same way > irl as I am here online. There is no persona, it's just me) I don't try to > dog either of them. We can have arguments, etc, and, still not take it > personal. As an actual peer would. > > Sorry for the long response, but, I don't have the free time I once had to > fiddle fart and fuck around. So I tend to condense things. Hopefully you're > okay with this and we can have reasonable adult conversations. The audacity of this post is truly staggering, but let me break it down in the most straightforward way possible. It’s clear from the way Gremlin writes that they have an inflated sense of their own technical prowess, but unfortunately, that doesn’t automatically make their knowledge infallible. Let’s take a closer look at the claims and the utterly self-serving rhetoric they use. First of all, Gremlin accuses someone (David) of not understanding basic technical matters—yet here they are, indulging in amateurish pseudo-intellectual chest-thumping. The fact that they feel the need to insert multiple tangential stories about their “impressive” career and childhood expertise only highlights their desperation to be recognized as an authority. It’s tiresome and reeks of insecurity. Yes, we get it—you’ve been around the block and have worked on a lot of machines, but this whole “I’ve been doing this since I was a kid” spiel doesn’t make you some kind of messiah of computer repair. It just makes you sound like someone trying way too hard to prove themselves to a crowd that frankly doesn’t care. Then, there’s the glaring inconsistency. They begin by arguing that the article David shared is wrong, dismissing it as a simple copy-paste job while simultaneously parroting the exact same points in a different context—nothing but a convoluted retelling of the same basic technical facts. The attempt to belittle David for “just copying and pasting” is laughable when Gremlin is doing the same thing but with more verbosity and an ego boost. Sure, the original article might not be perfect, but Gremlin’s response is more about puffing up their own knowledge rather than offering any new valuable insights. Let’s also address the supposed “diagnosis” of the machine problem. Gremlin’s attempt to position themselves as a seasoned tech guru is further undermined by their bizarre insistence that only they could get the right answer. It’s classic narcissism mixed with an unhealthy dose of self-importance, not to mention the assumption that everyone else involved is incompetent. The condescension oozing from the claim that others “didn’t know” or “got in the way” is typical of someone who can’t handle working with others in a collaborative space. The entire tone of the post—filled with insults, self-congratulatory bragging, and rewriting of past events—doesn’t show expertise; it shows someone who desperately craves validation. It’s almost comical how Gremlin criticizes others for being “trolls” when their entire post is nothing but trolling in the guise of technical discussion. It’s clear to anyone who reads this that Gremlin has an inflated view of their importance in these discussions and an almost pathological need to prove they’re superior. Instead of contributing to the conversation with humility or clarity, they choose to attack, belittle, and inflate their own relevance. Frankly, this approach does nothing but harm their credibility, which is exactly what we should be calling out. So, to wrap it up: if Gremlin really wants to be taken seriously, they should focus less on constant self-aggrandizement and more on actually contributing useful information to the conversation. Because right now, all they’re doing is inflating their ego at the expense of meaningful dialogue. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
| From | David <David@home.today> |
|---|---|
| Date | 2025-02-22 22:42 +0000 |
| Message-ID | <m1v276Fjpc3U3@mid.individual.net> |
| In reply to | #180402 |
On 22/02/2025 05:27, Gremlin wrote: > David <BD@invalid.email> news:m1hrelFjft2U2@mid.individual.net Mon, 17 Feb > 2025 22:27:33 GMT in alt.computer.workshop, wrote: > >> Malware *CAN* reside in places other than the main hard drive. Here are >> a few examples: > > I'm sure he's well aware of the methods you shared. You actually duplicated > atleast one...You did this because you don't actually understand things > concerning these machines on a technical level. For you, some of what can be > done with them appears to be black magic or something. At some point, you > assumed that some malware cannot be removed; once you have it, you have it > it's a done deal. That's not actually true, and I've tried to explain this > to you several times. You ignore me though and continue on with it. It is > somewhat annoying, but, I've learned to look over it. > >> 1. **USB Drives and External Storage**: Malware can infect USB drives, >> external hard drives, and SD cards. When these devices are plugged into >> a computer, the malware can execute or copy itself onto the system. > > Via auto run exploits if inserted into a windows based rig, otherwise > firmware modification; but again, it'll be OS specific. And with Linux, it > could even be distro specific. IE: works fine on say Linux Mint, but won't > work on MXLinux. They're based on different bases and this does sometimes > cause issues. > >> 2. **Firmware**: Some sophisticated malware targets the firmware of >> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >> It can persist through reboots and even OS reinstalls, making it harder >> to remove. > > It doesn't have to be sophisticated to go that route, but, most of the time > when they do firmware exploits, it's pretty advanced code with several > payloads. That's been my experience anyway. > >> 3. **Network Devices**: Certain malware can be embedded in devices like >> routers, network-attached storage (NAS) devices, or printers. These >> devices may have weak security and can serve as entry points for the >> malware to infect connected computers. > > This is one place where you duplicated yourself. It's firmware, bro. Instead > of doing a copy/paste, why don't you actually read the material and do what > we were taught to do as children? Acquire more details; research the matter > so that you have a solid understanding of what's being discussed. We used > to use actual books for that, but the internet made that task much easier. > You still have to actually do it tho. :) > >> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >> leaving no trace on the hard drive. This type of malware is often more >> challenging to detect, as it can vanish after a reboot. > > It still has to be loaded from a solid point to get into the RAM. And while > it's in solid form, if you don't use the host OS, you can hunt it down. All > Malware technically resides in RAM anyhow, they're programs like any other. > They just do things that they shouldn't be doing. But, at the end of the day > they are still programs, and can be treated the same as any other program. > > It's not possible to make truely undetectable malware David, is the point, > i'm trying to make here. It's quite possible to make it very difficult and > not possible with certain tools; but as I'm sure you understand, there's > more than one kind of tool. > >> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >> services or network shares. Once a device accesses these locations, it >> may download or spread the infection to other systems. > > That's a software issue. It's nothing new, and, I'd be hesitant to call that > an actual method. > >> 6. **Bootable Media**: In some cases, malware can reside on bootable >> media, such as CDs, DVDs, or even within boot sector code, and can >> execute before the operating system even loads. > > I'm well aware. It was one of the keypoints I raised with snit when he tried > his creative routine concerning some of what I wrote about a floppy hanging > a machine during boot if the bootsector didn't have pass along to HD based > os and transfer control. He conveniently leaves out my followup to my own > post where I got specific and asked why he'd allow the machine to even > attempt a floppy boot. Initially he claimed he was in charge of those > machines, but!, the moment I asked why he'd do that, he was quick to change > his tune and reverse course that he wasn't really in charge of them. > > A boot sector virus is a bit of a pain to write too, because you are very > limited on available physical space. If you're a complex critter, you have > to store the bulk of your code somewhere else, and load it later on. Or, > reconfigure the host to do that for you. You can just remain a tiny boot > sector virus and spread your code into other sectors that weren't in use, > but to protect your code, you went ahead and marked them as being in use so > the host OS wouldn't go and trash you when someone saved or created a file, > or did anything else to increase the space consumed. Even a swap file > adjustment could wreck your code and screw you good. code wise. > >> These types of malware often require different approaches to detection >> and removal since traditional antivirus tools mainly focus on scanning >> hard drives. > > This article you copy and pasted the contents from has issues, David. And > it's flatout wrong concerning the limitations of AV or what they spend the > bulk of their time scanning. Scanning for physical copies of malware is only > a section of their code. In order to properly write a self replicating > program that wasn't going to be tagged right off, you had to know how your > adversaries worked; I'm far from the only Vxer at the time who reverse > engineered the 'enemies' software. They do it to each other too, btw, they > just don't come outright and say that because it's a total violation of > various licensing agreements and they could actually be sued over it. > > AV companies do reverse engineer all software they encounter; malware and > legit software alike. They make no distinction other than to do a writeup on > the Malware and remain silent on what they learned from reverse engineering > their competitors. Multiple companies reverse engineered my BugHunter > program too; It's one of the reasons (the most important one imho) I wasn't > worried about people thinking it had a logic bomb or micky. If it did, I'd > have been exposed by all of the major players and destroy any chance I had > of redeeming myself and earning the respect as one of the mostly good guys. > I tried to explain this to Snit before, but, snit being snit wouldn't hear a > fucking word of it. As you and I both know, even if you choose not to admit > it in public, He's not a peer of mine and likely won't ever be. And, this > pisses him the fuck off. I'm not the only one who's tech savvy that he's > created a problem with. He does it in every technical newsgroup he joins. He > singles people like me out. He wants to be seen as a peer on the technical > fronts. > > And, I'm sure he's here because of you. Infact, the initial interaction he > had with me concerning 3D printing tech gave it away. Do you remember that? > He shared a url to a website that specialized in 3D printers and asked if I > could determine what kind of printer tech they were using. They openly > shared that information on the home page; I simply pointed that out to him, > everybody who visited the site could see the same information as I was > viewing. He was trying to talk down to me and do his thing. It didn't work > out for him. > > He's all about trying to bring up an 'ego' these days, doesn't want to > discuss points by point basis, just wants to use chatgpt and troll. He's > always been a troll mind you, but, he's not even trying to hide it these > days. Still lies his fucking ass off, and still tries to project his known > reading comprehension issues on me. He can't make the sale though, ffs, he > just pulls things entirely from his asshole. > > I think? I understand why you associate with him, but, David, he's not the > one who's going to bring me down. Once again, you've selected someone to > help you out that can't stand toe to toe with me. He never could. If you'll > recall, when the can we help him with his computer discussion started; I > asked him some questions about it when it was running, and then I shared my > initial diagnosis; that I don't think we have a mainboard problem, I think > we're looking at a bad hard drive. If you'll recall, SC did not initially > agree with my assesment. Which is understandable; he didn't know that I'm > actually a multi cert comp technician who's built and serviced tens of > thousands of machines during the course of my career. > > I wasn't asking Snit those questions randomly, and I didn't take a shot in > the dark guess on my diagnosis for the rig, I was going by decades of hands > on experience; actually working on them for a living. Not doing it on the > side from my house. I've done that too, on my off days, but I have an actual > lab here to do that stuff with. It's basically a duplicate of everything I > was able to access at the shop I worked for. My former employer insisted I > do this due to my health; some days I just couldn't go in and stay all day, > but I could swing by and pickup a few machines to work on, to lighten the > shops load. > > Back then you really needed multiple computers to assist you with repairs. > That's especially true today. You could get buy using the only PC you had if > you were in a bind, but, it's much more efficient to have multiple machines > available to you. You can assign tasks more efficiently that way. Especially > with data recovery efforts, that can take hours to days and the machine > doing the task is tied up, focused entirely on that single project. It's not > wise to try and use said machine while it's in the middle of data recovery. > you may not get a 2nd chance to pull data if it's interrupted. > > And, as you well know, my diagnosis was confirmed as being accurate, despite > Snits efforts to stall and take his sweet time, deliberately ignoring my > specific instructions and taking 'help' from anyone who posted. That > actually makes troubleshooting remotely a bit of a pain. Time is wasted, and > it only adds to possible confusion for him. I tried to explain this to you > and SC; but you guys refused to just lemme do my thing. I'd have had that > confirmed diagnosis a lot sooner if you guys had remained on the sidelines. > I understand, you were both trying to help; but when you're actually serious > about the trade, you don't do that. > > It's too many chiefs and too few indians then, you understand? I'm not > trying to insult either of you, btw, I'm just reminding you of things. The > two of you were basically, I think without even realizing it, helping Snit > try to make me look incompetent. That was the actual reason he agreed to let > me try and diagnose his machine via usenet; He didn't think I'd actually be > able to. He thought I was BSing, just as he thought I wasn't actually Raid > for a long time. Until well, enough proof was posted that he couldn't > continue making that claim. It just wasn't working out. Now he's trying to > sell the story that he never did that. Now he's trying to say I accused him > of not posting as Raid or some completely unrelated bullshit; that wasn't > what I accused him of. And you know that. I was rightfully accusing him of > lieing and spinning things around. Which publically agree or not, you know > damn well that's part of what he does here. > > I do understand why SC disagreed with my initial diagnosis; that's where > hands on experience comes into play, in my favor in this case. I've never > been what you call a hobbyist level computer user. My experience isn't > limited to fixing friends and family computers as time allowed. I actually > did it, every day, for a living. I didn't even spend a solid hour doing my > CompTIA testing, David. I was high at the time and I fucked around; but I > still passed with 95% average. Had I actually dedicated myself to it, I'd > have 0wned it outright. I'm not a hobbyist repair person friends and family > call; I have considerably more hands on experience from repairing hardware > to software. FFS, I've rebuilt a corrupted windows registry hive by hand > using a hex editor and writing little tools with ASIC to patch bytes. It > took me 3 fucking hours, but I did it. Why didn't I just reload it? Well, > that machine ran a plasma cutter that used proprietary as fuck software with > a dongle and he had no way to reinstall it; lost the cdrom a long time ago. > And despite my efforts to find a suitable copy online that would > specifically run that hardware; It was deuces. So, if I couldn't keep the > software in working condition, there was no point in going any further with > the rig. It would either be able to run that huge plasma cutter or it > wouldn't. And if it didn't, we didn't get paid for the job. Boss didn't like > non paying jobs very much. It was in my best interest to repair whatever > machine came onto my bench. > > I didn't always have the luxury of rename windows directories and reload, or > wipe and reload. Sometimes, the machine had very specific software that > required you actually be a real Technician because you'd be doing what had > to be done to restore the OS and software, without reloading; because as I > wrote above, that wasn't an option. I've always hated that 'fix' methodology > too, because if you really know what the fuck you're doing, you should not > have to resort to a clean reload. Anybody can wipe and reload a box, you do > it all the fucking time. > > SC probably thought I was getting ahead of myself. But, again, I remind you > I asked snit specific questions about the machines behavior and they weren't > random ones. I was getting a feel for the status, mostly due to the way in > which he described it began to fail on him. My decades of fixing these > fucking things for a living is what lead me to that diagnosis. You have to > understand, I've been repairing these rigs since before I was even a > teenager; that's how I made money as a kid going to school. I didn't grow up, > become an adult, and then decide 'hey I wanna work on computers and > electronics' I was *already doing that* and had been since I was literally, > a little kid. > > Snit will come along and accuse me of having a huge ego here, I've little > doubt. But, I'm sure you know this has fuckall to do with any ego on my part. > I'm simply being blunt candid and honest. There's no ego here, I have > nothing to prove.. My own known history did that for me. You read what > chatgpt actually knows about me, you've even shared some of it's information > on me here. I'm not an ego driven maniac that snits working so hard to paint > me out as; when he could be more productive and work for a living. > > If I was, you wouldn't have interacted with me beyond the first couple of > emails between us. Snit's just using that as his latest bullshit excuse for > his inability to keep up with me. A situation he put himself in, too, btw. I > wasn't trying to 'compete' with him or anyone else here. I respect (greatly) > two of the posters especially, and you know them both. And you know why I > hold them in such high regard too. > > They are, 100%, peers of mine. We're on the same level for the most part. > Perhaps some skillset differences due to personal interest differences, but > at the end of the day, they're just as competent as I am. I do not question > the advice they provide others here when they choose to do so; I'm sure > you've noticed that. I'm also sure you've noticed that when either of them > or both disagrees with me, I still remain respectful (er for the most part > anyhow. I do have a sailors mouth, after all. And, I really am the same way > irl as I am here online. There is no persona, it's just me) I don't try to > dog either of them. We can have arguments, etc, and, still not take it > personal. As an actual peer would. > > Sorry for the long response, but, I don't have the free time I once had to > fiddle fart and fuck around. So I tend to condense things. Hopefully you're > okay with this and we can have reasonable adult conversations. HOW would you like me to respond to this, Dustin? -- David
[toc] | [prev] | [next] | [standalone]
| From | Brock McNuggets <brock.mcnuggets@gmail.com> |
|---|---|
| Date | 2025-02-22 23:08 +0000 |
| Message-ID | <67ba5900$0$2757$882e4bbb@reader.netnews.com> |
| In reply to | #180428 |
On Feb 22, 2025 at 3:42:44 PM MST, "David" wrote <m1v276Fjpc3U3@mid.individual.net>: > On 22/02/2025 05:27, Gremlin wrote: >> David <BD@invalid.email> news:m1hrelFjft2U2@mid.individual.net Mon, 17 Feb >> 2025 22:27:33 GMT in alt.computer.workshop, wrote: >> >>> Malware *CAN* reside in places other than the main hard drive. Here are >>> a few examples: >> >> I'm sure he's well aware of the methods you shared. You actually duplicated >> atleast one...You did this because you don't actually understand things >> concerning these machines on a technical level. For you, some of what can be >> done with them appears to be black magic or something. At some point, you >> assumed that some malware cannot be removed; once you have it, you have it >> it's a done deal. That's not actually true, and I've tried to explain this >> to you several times. You ignore me though and continue on with it. It is >> somewhat annoying, but, I've learned to look over it. >> >>> 1. **USB Drives and External Storage**: Malware can infect USB drives, >>> external hard drives, and SD cards. When these devices are plugged into >>> a computer, the malware can execute or copy itself onto the system. >> >> Via auto run exploits if inserted into a windows based rig, otherwise >> firmware modification; but again, it'll be OS specific. And with Linux, it >> could even be distro specific. IE: works fine on say Linux Mint, but won't >> work on MXLinux. They're based on different bases and this does sometimes >> cause issues. >> >>> 2. **Firmware**: Some sophisticated malware targets the firmware of >>> devices like the BIOS or UEFI (Unified Extensible Firmware Interface). >>> It can persist through reboots and even OS reinstalls, making it harder >>> to remove. >> >> It doesn't have to be sophisticated to go that route, but, most of the time >> when they do firmware exploits, it's pretty advanced code with several >> payloads. That's been my experience anyway. >> >>> 3. **Network Devices**: Certain malware can be embedded in devices like >>> routers, network-attached storage (NAS) devices, or printers. These >>> devices may have weak security and can serve as entry points for the >>> malware to infect connected computers. >> >> This is one place where you duplicated yourself. It's firmware, bro. Instead >> of doing a copy/paste, why don't you actually read the material and do what >> we were taught to do as children? Acquire more details; research the matter >> so that you have a solid understanding of what's being discussed. We used >> to use actual books for that, but the internet made that task much easier. >> You still have to actually do it tho. :) >> >>> 4. **RAM**: Some malware operates purely in the system's memory (RAM), >>> leaving no trace on the hard drive. This type of malware is often more >>> challenging to detect, as it can vanish after a reboot. >> >> It still has to be loaded from a solid point to get into the RAM. And while >> it's in solid form, if you don't use the host OS, you can hunt it down. All >> Malware technically resides in RAM anyhow, they're programs like any other. >> They just do things that they shouldn't be doing. But, at the end of the day >> they are still programs, and can be treated the same as any other program. >> >> It's not possible to make truely undetectable malware David, is the point, >> i'm trying to make here. It's quite possible to make it very difficult and >> not possible with certain tools; but as I'm sure you understand, there's >> more than one kind of tool. >> >>> 5. **Cloud Storage or Network Shares**: Malware can infect cloud storage >>> services or network shares. Once a device accesses these locations, it >>> may download or spread the infection to other systems. >> >> That's a software issue. It's nothing new, and, I'd be hesitant to call that >> an actual method. >> >>> 6. **Bootable Media**: In some cases, malware can reside on bootable >>> media, such as CDs, DVDs, or even within boot sector code, and can >>> execute before the operating system even loads. >> >> I'm well aware. It was one of the keypoints I raised with snit when he tried >> his creative routine concerning some of what I wrote about a floppy hanging >> a machine during boot if the bootsector didn't have pass along to HD based >> os and transfer control. He conveniently leaves out my followup to my own >> post where I got specific and asked why he'd allow the machine to even >> attempt a floppy boot. Initially he claimed he was in charge of those >> machines, but!, the moment I asked why he'd do that, he was quick to change >> his tune and reverse course that he wasn't really in charge of them. >> >> A boot sector virus is a bit of a pain to write too, because you are very >> limited on available physical space. If you're a complex critter, you have >> to store the bulk of your code somewhere else, and load it later on. Or, >> reconfigure the host to do that for you. You can just remain a tiny boot >> sector virus and spread your code into other sectors that weren't in use, >> but to protect your code, you went ahead and marked them as being in use so >> the host OS wouldn't go and trash you when someone saved or created a file, >> or did anything else to increase the space consumed. Even a swap file >> adjustment could wreck your code and screw you good. code wise. >> >>> These types of malware often require different approaches to detection >>> and removal since traditional antivirus tools mainly focus on scanning >>> hard drives. >> >> This article you copy and pasted the contents from has issues, David. And >> it's flatout wrong concerning the limitations of AV or what they spend the >> bulk of their time scanning. Scanning for physical copies of malware is only >> a section of their code. In order to properly write a self replicating >> program that wasn't going to be tagged right off, you had to know how your >> adversaries worked; I'm far from the only Vxer at the time who reverse >> engineered the 'enemies' software. They do it to each other too, btw, they >> just don't come outright and say that because it's a total violation of >> various licensing agreements and they could actually be sued over it. >> >> AV companies do reverse engineer all software they encounter; malware and >> legit software alike. They make no distinction other than to do a writeup on >> the Malware and remain silent on what they learned from reverse engineering >> their competitors. Multiple companies reverse engineered my BugHunter >> program too; It's one of the reasons (the most important one imho) I wasn't >> worried about people thinking it had a logic bomb or micky. If it did, I'd >> have been exposed by all of the major players and destroy any chance I had >> of redeeming myself and earning the respect as one of the mostly good guys. >> I tried to explain this to Snit before, but, snit being snit wouldn't hear a >> fucking word of it. As you and I both know, even if you choose not to admit >> it in public, He's not a peer of mine and likely won't ever be. And, this >> pisses him the fuck off. I'm not the only one who's tech savvy that he's >> created a problem with. He does it in every technical newsgroup he joins. He >> singles people like me out. He wants to be seen as a peer on the technical >> fronts. >> >> And, I'm sure he's here because of you. Infact, the initial interaction he >> had with me concerning 3D printing tech gave it away. Do you remember that? >> He shared a url to a website that specialized in 3D printers and asked if I >> could determine what kind of printer tech they were using. They openly >> shared that information on the home page; I simply pointed that out to him, >> everybody who visited the site could see the same information as I was >> viewing. He was trying to talk down to me and do his thing. It didn't work >> out for him. >> >> He's all about trying to bring up an 'ego' these days, doesn't want to >> discuss points by point basis, just wants to use chatgpt and troll. He's >> always been a troll mind you, but, he's not even trying to hide it these >> days. Still lies his fucking ass off, and still tries to project his known >> reading comprehension issues on me. He can't make the sale though, ffs, he >> just pulls things entirely from his asshole. >> >> I think? I understand why you associate with him, but, David, he's not the >> one who's going to bring me down. Once again, you've selected someone to >> help you out that can't stand toe to toe with me. He never could. If you'll >> recall, when the can we help him with his computer discussion started; I >> asked him some questions about it when it was running, and then I shared my >> initial diagnosis; that I don't think we have a mainboard problem, I think >> we're looking at a bad hard drive. If you'll recall, SC did not initially >> agree with my assesment. Which is understandable; he didn't know that I'm >> actually a multi cert comp technician who's built and serviced tens of >> thousands of machines during the course of my career. >> >> I wasn't asking Snit those questions randomly, and I didn't take a shot in >> the dark guess on my diagnosis for the rig, I was going by decades of hands >> on experience; actually working on them for a living. Not doing it on the >> side from my house. I've done that too, on my off days, but I have an actual >> lab here to do that stuff with. It's basically a duplicate of everything I >> was able to access at the shop I worked for. My former employer insisted I >> do this due to my health; some days I just couldn't go in and stay all day, >> but I could swing by and pickup a few machines to work on, to lighten the >> shops load. >> >> Back then you really needed multiple computers to assist you with repairs. >> That's especially true today. You could get buy using the only PC you had if >> you were in a bind, but, it's much more efficient to have multiple machines >> available to you. You can assign tasks more efficiently that way. Especially >> with data recovery efforts, that can take hours to days and the machine >> doing the task is tied up, focused entirely on that single project. It's not >> wise to try and use said machine while it's in the middle of data recovery. >> you may not get a 2nd chance to pull data if it's interrupted. >> >> And, as you well know, my diagnosis was confirmed as being accurate, despite >> Snits efforts to stall and take his sweet time, deliberately ignoring my >> specific instructions and taking 'help' from anyone who posted. That >> actually makes troubleshooting remotely a bit of a pain. Time is wasted, and >> it only adds to possible confusion for him. I tried to explain this to you >> and SC; but you guys refused to just lemme do my thing. I'd have had that >> confirmed diagnosis a lot sooner if you guys had remained on the sidelines. >> I understand, you were both trying to help; but when you're actually serious >> about the trade, you don't do that. >> >> It's too many chiefs and too few indians then, you understand? I'm not >> trying to insult either of you, btw, I'm just reminding you of things. The >> two of you were basically, I think without even realizing it, helping Snit >> try to make me look incompetent. That was the actual reason he agreed to let >> me try and diagnose his machine via usenet; He didn't think I'd actually be >> able to. He thought I was BSing, just as he thought I wasn't actually Raid >> for a long time. Until well, enough proof was posted that he couldn't >> continue making that claim. It just wasn't working out. Now he's trying to >> sell the story that he never did that. Now he's trying to say I accused him >> of not posting as Raid or some completely unrelated bullshit; that wasn't >> what I accused him of. And you know that. I was rightfully accusing him of >> lieing and spinning things around. Which publically agree or not, you know >> damn well that's part of what he does here. >> >> I do understand why SC disagreed with my initial diagnosis; that's where >> hands on experience comes into play, in my favor in this case. I've never >> been what you call a hobbyist level computer user. My experience isn't >> limited to fixing friends and family computers as time allowed. I actually >> did it, every day, for a living. I didn't even spend a solid hour doing my >> CompTIA testing, David. I was high at the time and I fucked around; but I >> still passed with 95% average. Had I actually dedicated myself to it, I'd >> have 0wned it outright. I'm not a hobbyist repair person friends and family >> call; I have considerably more hands on experience from repairing hardware >> to software. FFS, I've rebuilt a corrupted windows registry hive by hand >> using a hex editor and writing little tools with ASIC to patch bytes. It >> took me 3 fucking hours, but I did it. Why didn't I just reload it? Well, >> that machine ran a plasma cutter that used proprietary as fuck software with >> a dongle and he had no way to reinstall it; lost the cdrom a long time ago. >> And despite my efforts to find a suitable copy online that would >> specifically run that hardware; It was deuces. So, if I couldn't keep the >> software in working condition, there was no point in going any further with >> the rig. It would either be able to run that huge plasma cutter or it >> wouldn't. And if it didn't, we didn't get paid for the job. Boss didn't like >> non paying jobs very much. It was in my best interest to repair whatever >> machine came onto my bench. >> >> I didn't always have the luxury of rename windows directories and reload, or >> wipe and reload. Sometimes, the machine had very specific software that >> required you actually be a real Technician because you'd be doing what had >> to be done to restore the OS and software, without reloading; because as I >> wrote above, that wasn't an option. I've always hated that 'fix' methodology >> too, because if you really know what the fuck you're doing, you should not >> have to resort to a clean reload. Anybody can wipe and reload a box, you do >> it all the fucking time. >> >> SC probably thought I was getting ahead of myself. But, again, I remind you >> I asked snit specific questions about the machines behavior and they weren't >> random ones. I was getting a feel for the status, mostly due to the way in >> which he described it began to fail on him. My decades of fixing these >> fucking things for a living is what lead me to that diagnosis. You have to >> understand, I've been repairing these rigs since before I was even a >> teenager; that's how I made money as a kid going to school. I didn't grow up, >> become an adult, and then decide 'hey I wanna work on computers and >> electronics' I was *already doing that* and had been since I was literally, >> a little kid. >> >> Snit will come along and accuse me of having a huge ego here, I've little >> doubt. But, I'm sure you know this has fuckall to do with any ego on my part. >> I'm simply being blunt candid and honest. There's no ego here, I have >> nothing to prove.. My own known history did that for me. You read what >> chatgpt actually knows about me, you've even shared some of it's information >> on me here. I'm not an ego driven maniac that snits working so hard to paint >> me out as; when he could be more productive and work for a living. >> >> If I was, you wouldn't have interacted with me beyond the first couple of >> emails between us. Snit's just using that as his latest bullshit excuse for >> his inability to keep up with me. A situation he put himself in, too, btw. I >> wasn't trying to 'compete' with him or anyone else here. I respect (greatly) >> two of the posters especially, and you know them both. And you know why I >> hold them in such high regard too. >> >> They are, 100%, peers of mine. We're on the same level for the most part. >> Perhaps some skillset differences due to personal interest differences, but >> at the end of the day, they're just as competent as I am. I do not question >> the advice they provide others here when they choose to do so; I'm sure >> you've noticed that. I'm also sure you've noticed that when either of them >> or both disagrees with me, I still remain respectful (er for the most part >> anyhow. I do have a sailors mouth, after all. And, I really am the same way >> irl as I am here online. There is no persona, it's just me) I don't try to >> dog either of them. We can have arguments, etc, and, still not take it >> personal. As an actual peer would. >> >> Sorry for the long response, but, I don't have the free time I once had to >> fiddle fart and fuck around. So I tend to condense things. Hopefully you're >> okay with this and we can have reasonable adult conversations. > > HOW would you like me to respond to this, Dustin? With anger, hatred, blame against me... and adoration toward him. In short you need to join into his delusions. -- Specialist in unnecessary details and overcomplicated solutions.
[toc] | [prev] | [next] | [standalone]
Page 5 of 7 — ← Prev page 1 2 3 4 [5] 6 7 Next page →
Back to top | Article view | uk.comp.sys.mac
csiph-web