Update your software now!

"David B." on Mon, 17 Jun 2019 10:30:43
+0100 typed in alt.windows7.general the following:
On 17/06/2019 02:35, pyotr filipivich wrote:
"David B." on Sun, 16 Jun 2019 17:58:15
+0100 typed in alt.windows7.general the following:

An updated O/s probably wouldn't run on my computer -- not enough
resources. People are using Windows XP because they aren't rich enough
to buy a new computer every few months.

IIRC, I started using Windows XP when it was first introduced in 2002 -
it really is 'old hat' now! If you drove a motor vehicle of that age you
might well expect it to suffer more breakdowns than a new or nearly new car!

What is in a Operating System comparable to the mechanical items
in an automobile, which can wear out?

Will 'vulnerabilities' suffice?

No.

You were saying that an OS wears as it runs, and eventually fails
due to something wearing out.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

"Apd" on Mon, 17 Jun 2019 12:30:22 +0100 typed in
alt.windows7.general the following:
"David B." wrote:
On 17/06/2019 02:35, pyotr filipivich wrote:
"David B." on Sun, 16 Jun 2019 17:58:15 wrote:
Steve Hayes wrote:
An updated O/s probably wouldn't run on my computer -- not enough
resources. People are using Windows XP because they aren't rich enough
to buy a new computer every few months.

People are also using XP because they don't need or don't like later
Microsoft OSes.

And many people, like myself, are quite indifferent to the changes
made to the OS*, it is the Interface which ticks us off.


tschus
pyotr

* as far as I am concerned, when I press the "a" key, it doesn't
matter if the letter "a" appears on the screen due to electrons or
elves.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?

"David B." wrote:
On 17/06/2019 12:30, Apd wrote:
People are also using XP because they don't need or don't like later
Microsoft OSes.

I don't think that's true. Even I use XP sometimes - because I can, but
I much prefer to use my pristine Apple iMac! ;-)

It is true. I use it in preference to Win7 which I have on a laptop. I
have a few machines running XP and one is an iMac (2006). XP supports
a more recent version of Firefox than the Mac OS of that time will.

Old cars don't have vulnerabilities. Any design faults they may have
will be well-known and will have fixes or work-arounds.

Not so much nowadays, but the major killer of cars during my lifetime
has been *rust*! Think Vauxhall Victor, Lancia Fulvia or any Subaru

Yes, also Ford Zodiacs and such. My current car is from 2002 (same age
as XP) and is what I consider modern. There's no sign of rust on the
bodywork and it still passes MOTs without trouble and runs well.

On 17/06/2019 18:41, pyotr filipivich wrote:
"David B." on Mon, 17 Jun 2019 10:30:43
+0100 typed in alt.windows7.general the following:
On 17/06/2019 02:35, pyotr filipivich wrote:
"David B." on Sun, 16 Jun 2019 17:58:15
+0100 typed in alt.windows7.general the following:

An updated O/s probably wouldn't run on my computer -- not enough
resources. People are using Windows XP because they aren't rich enough
to buy a new computer every few months.

IIRC, I started using Windows XP when it was first introduced in 2002 -
it really is 'old hat' now! If you drove a motor vehicle of that age you
might well expect it to suffer more breakdowns than a new or nearly new car!

What is in a Operating System comparable to the mechanical items
in an automobile, which can wear out?

Will 'vulnerabilities' suffice?

No.

You were saying that an OS wears as it runs, and eventually fails
due to something wearing out.

Well, FWIW, there's something not quite right about this:-

https://www.virustotal.com/gui/url/8...3427/detection

--
David B.
Devon, UK

David B. wrote:


I expect you know all about THIS already .....

https://www.us-cert.gov/ncas/alerts/AA19-168A

If you read the content of that page, you'd realize that
it doesn't tell a WinXP user where to get their KB file
or what KB number it is.

A number of similar web pages, fail in a similar way.

This is why we cannot hand out the first page we find,
knowing that information is missing.

If I was cooking up URLs to hand out, I'd at least
want a page with a full list. The "official" pages
are not helpful for a WinXP user.

Paul

On 17/06/2019 19:58, Paul wrote:
David B. wrote:


I expect you know all about THIS already .....

https://www.us-cert.gov/ncas/alerts/AA19-168A

If you read the content of that page, you'd realize that
it doesn't tell a WinXP user where to get their KB file
or what KB number it is.

A number of similar web pages, fail in a similar way.

This is why we cannot hand out the first page we find,
knowing that information is missing.

If I was cooking up URLs to hand out, I'd at least
want a page with a full list. The "official" pages
are not helpful for a WinXP user.

Â*Â* Paul


The link to THIS page was shown on the page I posted, Paul.

https://support.microsoft.com/en-us/...-cve-2019-0708

Is this what you require?

--
David B.
Devon, UK

David B. wrote:
Paul wrote:
David B. wrote:


I expect you know all about THIS already .....

https://www.us-cert.gov/ncas/alerts/AA19-168A

If you read the content of that page, you'd realize that
it doesn't tell a WinXP user where to get their KB file
or what KB number it is.

A number of similar web pages, fail in a similar way.

This is why we cannot hand out the first page we find,
knowing that information is missing.

If I was cooking up URLs to hand out, I'd at least
want a page with a full list. The "official" pages
are not helpful for a WinXP user.


The link to THIS page was shown on the page I posted, Paul.

https://support.microsoft.com/en-us/...-cve-2019-0708


Is this what you require?

The XP kb # is in the 2nd column of the table at that link, 4500331.

A good way for the us-cert site to have handled such as the XP item
would be to mention 4500331. Likewise 4499180 for vista.

--
Mike Easter

On 17/06/2019 21:28, Mike Easter wrote:
David B. wrote:
Paul wrote:
David B. wrote:


I expect you know all about THIS already .....

https://www.us-cert.gov/ncas/alerts/AA19-168A

If you read the content of that page, you'd realize that
it doesn't tell a WinXP user where to get their KB file
or what KB number it is.

A number of similar web pages, fail in a similar way.

This is why we cannot hand out the first page we find,
knowing that information is missing.

If I was cooking up URLs to hand out, I'd at least
want a page with a full list. The "official" pages
are not helpful for a WinXP user.


The link to THIS page was shown on the page I posted, Paul.

https://support.microsoft.com/en-us/...-cve-2019-0708


Is this what you require?

The XP kb # is in the 2nd column of the table at that link, 4500331.

A good way for the us-cert site to have handled such as the XP item
would be to mention 4500331.Â* Likewise 4499180 for vista.

If you wish, you may provide feedback he-

https://www.us-cert.gov/forms/feedback

Will you do so?

David B. wrote:
Will you do so?

I'll leave such meddlesome activity up to those who like to meddle. And
pry and snoop.

--
Mike Easter

On 17/06/2019 21:40, Mike Easter wrote:
David B. wrote:
Will you do so?

I'll leave such meddlesome activity up to those who like to meddle.Â* And
pry and snoop.

It's best that Americans report problems with American government issues
so I'll leave well alone.

Are there any more of the unanswered questions I've asked you recently
which you'd be willing to revisit?

(Follow-up set to 'my' group).

"Mike Easter" wrote

| The XP kb # is in the 2nd column of the table at that link, 4500331.
|

For that one there's a better way:

http://download.windowsupdate.com/c/...2da0421188.exe

Cut out the middleman.

Win7-64:

http://download.windowsupdate.com/d/...75e49b58cb.msu

On 17/06/2019 21:54, Mayayana wrote:
"Mike Easter" wrote

| The XP kb # is in the 2nd column of the table at that link, 4500331.
|

For that one there's a better way:

http://download.windowsupdate.com/c/...2da0421188.exe

Cut out the middleman.

Win7-64:

http://download.windowsupdate.com/d/...75e49b58cb.msu

Thanks, Mayayana.

Had you already actioned matters or was my post actually helpful to you?

--
David B.
Devon, UK

On 17/06/2019 03:55, Steve Hayes wrote:
On Sun, 16 Jun 2019 17:58:15 +0100, "David B."
wrote:

On 16/06/2019 16:31, Steve Hayes wrote:
So why are you posting this here?

It's important information propagated by the US government.

Many folk just don't understand how sophisticated the 'bad guys' have
become - they can run rings around the average computer user.

I'm sure they can, but most of them don't waste their time on the
diminishing number of people using older computers, who've usual;ly
been around long enough to know that you shouldn't open unsolicited
e-mail attachments and things like that.

I expect you know all about i-frames and MIM attacks too. Just visiting
a URL can infect a Windows XP computer!

An updated O/s probably wouldn't run on my computer -- not enough
resources. People are using Windows XP because they aren't rich enough
to buy a new computer every few months.

IIRC, I started using Windows XP when it was first introduced in 2002 -
it really is 'old hat' now! If you drove a motor vehicle of that age you
might well expect it to suffer more breakdowns than a new or nearly new car!

Perhaps.

I drive a 2001 Subaru Legacy, for the same reason. It hasn't broken
down yet.

Excellent vehicle ....... as long as it doesn't suffer from rust!

Internet browsers and apps. Both are access points for criminals to
enter your devices, so it’s important to keep them secure.

I downdated my browser when it got too bloated to run on my OS. The
newest version tells me it won't run at all, get a new computer.
Whuich means getyting a new2 OS, and finding that hal my software
won't run on it.

Then it's probably time to change your software too, Steve! ;-)

Send me US$ 10000 and I'll do it.

Did you read about this?

https://edition.cnn.com/2017/04/13/a...ria/index.html

I bet you wish you'd answered those unsolicited emails now! ;-D

--
David B.
Devon, UK

David B. wrote:
On 17/06/2019 21:40, Mike Easter wrote:
David B. wrote:
Will you do so?

I'll leave such meddlesome activity up to those who like to meddle.
And pry and snoop.

It's best that Americans report problems with American government issues
so I'll leave well alone.

Are there any more of the unanswered questions I've asked you recently
which you'd be willing to revisit?

(Follow-up set to 'my' group).

David, if you know how the system works, you
wouldn't need to make this suggestion.

The company reporting the CVE, creates the content. The
officiating body, does not "rewrite someone elses submission",
because that would be cheeky. The submitter controls the
information flow.

You'll only be told to take up your complaint
in this case, with the writer at Microsoft who
prepared the materials.

Microsoft wanted us to "bob for apples", and bob
for apples we must. Complaining will get you "squat".

Paul

David B. wrote:
On 17/06/2019 21:54, Mayayana wrote:
"Mike Easter" wrote

| The XP kb # is in the 2nd column of the table at that link, 4500331.
|

For that one there's a better way:

http://download.windowsupdate.com/c/...2da0421188.exe


Cut out the middleman.

Win7-64:

http://download.windowsupdate.com/d/...75e49b58cb.msu


Thanks, Mayayana.

Had you already actioned matters or was my post actually helpful to you?


I previously acquired the materials and tagged them
for future consumption. Acquired 05/31/2019 or so.

TerminalServicesRDPnoAuth-WORM
windows6.1-kb4499175-x64_3704acfff45ddf163d8049683d5a3b75e49b58cb.msu
windows6.1-kb4499175-x86_6f1319c32d5bc4caf2058ae8ff40789ab10bf41b.msu
windowsxp-kb4500331-x86-custom-enu_d7206aca53552fececf72a3dee93eb2da0421188.exe
windowsxp-kb4500331-x86-custom-enu_d7206aca53552fececf72a3dee93eb2da0421188__RDP_ patch.exe

For a WinXP user, the SMBV1 would be like this. 05/31/2017

windowsxp-kb4012598-x86-custom-enu_eceb7d5023bbb23c0dc633e46b9c2f14fa6ee9dd__SMBv 1.exe

Paul