~BD~ <~BD~@nomail.afraid.com> wrote in
news:ir7viq$e97$1@dont-email.me:

>> What's saddest tho, is that you will never be able to help anyone
>> find any bad guys. You don't have the skills and you never will
>> acquire them at this rate. You continue to alienate all who could
>> in some fashion be of use to you.
>
> A number of articles have been posted that discuss attribution for
> the Stuxnet cyberattack. Attribution is tricky — I’ve been there
> and made that mistake. The articles actually named China, Israel,
> United Kingdom and the United States as being behind what has come
> to be known as the most sophisticated cyber weapon and attack seen
> to date, at least in the public domain.

This isn't your style of writing.. Copy/pasted?

> Ref:
> http://gcn.com/Articles/2011/02/28/D...xnet-Mystery-c
> yberattack.aspx?sc_lang=en&Page=1

Ahh, yep.. see above.

>> You need to learn basic html and basic networking 101 before the
>> article and the tools will make any real sense to you. Until you
>> decide to take the plunge and learn something, you're screwed.
>
> As you can see from the extract from the article above, there's no
> way that I could ever hope to develop sufficient skills - technical
> skills, that is!

Your efforts to hunt bad guys are a lost cause then. Until you
understand them and can discuss the technology which is their world,
you're screwed.

> If catching bad guys relied solely on technical skill, us good guys
> would /never/ win! ;-)

For the most part, in the digital age, it does and you typically don't
win.

> OK, I thought, I'll do just that! Turn back the clock 30 years and
> learn it all again!

Turn back the clock? Nasm is still updated. [g]
Assembler might be old, but it's still useful and needed. Think of the
malware researchers. Sadly, some aren't actually programmers (let
alone coders) so they are limited in what they can do. Then you have
the coders bunch, we aren't limited in such a manner. We can take the
program apart and have a look around.

I won't provide you names of those who do/don't code, either, so don't
bother asking.

> You'll note the 's' after http - I was therefore rather surprised
> that, in three separate browsers, I got a security warning pop up
> when I went to that URL! Here's an example:

I've noticed you avoided the simple task I provided you, yes. And
instead are asking about SSL again. (that's the [s] in http(s))

> *Is that a reasonable thing to occur*? <shrug> I just don't know.

You have been told and told and told and told how SSL works. It's time
for you to use google, now.

> In this lesson, you'll learn what it takes to properly maintain a
> wired or wireless network. You'll learn about network performance
> optimization, how to make sure your network is secure and how to
> establish a network maintenance routine.


Many will, many have. I have my doubts with regards to you
specifically tho.



--
Why drink the water from my hand?
Contagious as you think I am
Just tilt my sun towards your domain
Your cup runneth over again