Scheduled task problem

P

Phil Weldon

'Craig Schiller' wrote:
| My apologies. Since I was the OP, I thought that was aimed at me.
|
| Peace.

By the way, if the email address identity is real, you are inviting every
spammer in the world to add to your burden.
Spammers use automated programs to scour Usenet newsgroups for anything that
looks like an email address. Even worse, some Internet worms (like 'Swen')
run on infected systems harvesting email addresses from Usenet newsgroups,
then use these address as the 'To:' address for infected email and as a
faked 'From:' address of infected email.

Set up your 'Mozilla' with a guaranteed invalid email address to appear with
your posts ('example.com' is a domain name set aside specifically for
examples, and cannot be a valid domain name; 'invalid.com' is also reserved
and can not be a valid domain name - by using something like
'(e-mail address removed)' you insure that spam meant for you does not
appear in an innocent email box.)

Also keep in mind that Google keeps newsgroup posts effectively forever in a
searchable form. What you post becomes a permanent part of the Internet.
This newsgroup, microsoft.public.windowsxp.basics is effectively a Usenet
newsgroup, and is under no real control by Microsoft or anyone else (though
NSA is working on it.)

Phil Weldon

| My apologies. Since I was the OP, I thought that was aimed at me.
|
| Peace.
|
| Craig
|
| David Candy wrote:
|
| > Well I wasn't talking to you. And it is an idiotic thing to say. What he
is saying is "this is how to allow anyone in the world, incl anyone without
technical skills, to hack into your computer"
| >
|
 
D

David Candy

Just don't follow his advice. It's dangerous. For a year a patiently explained why. Till everyone finally realised how and why it is dangerous. It has it's uses, but not on a computer connected to the internet or corporate network.

People need to research the consequences of things they find.

This is from Help in Local Security Policy re LimitBlankPassword

Accounts: Limit local account use of blank passwords to console logon only
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

Description
Determines whether remote interactive logons by network services such as Terminal Services, Telnet, and FTP are allowed for local accounts that have blank passwords. If this setting is enabled, a local account must have a nonblank password to be used to perform an interactive logon from a remote client.

Default: Enabled

Notes

a.. This setting does not affect interactive logons that are performed physically at the console.
b.. This setting does not affect logons that use domain accounts.
c.. It is possible for applications that use remote interactive logons to bypass this setting.
For more information, see:

a.. Security Configuration Manager Tools
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top