Fake MicroSoft calls Post: 303011356

Sponsored Content

Special Forums Cybersecurity Fake MicroSoft calls Post 303011356 by RudiC on Wednesday 17th of January 2018 07:25:55 AM

01-17-2018

Registered User

Fake MicroSoft calls

Dear colleagues,

it's that time of the year again: in recent days and weeks I'm receiving annoying numbers of annoying "support" calls from dubious "MicroSoft Centers" telling me that my computer generates errors and / or downloads malicious SW. Although ignoring these pesterers on the phone, I'm a bit concerned as I can't assess the danger they pose, coming in via VoIP.
Very few ports are open on my PC interface: SunRPC and 766 (both listened on by rpcbind), CUPS, DNS and Link-Local Multicast Name Resolution (both listened on by systemd-resolve). On my router, none of the common ports is open to the WAN.
No indication (yet) of remote interaction (attempts) in my system log file.

Does anyone of you have an idea or indication, what the threat would be and how I could prevent any damage? Can they, from VoIP connection / communication data, infer / deduct / extract information allowing them to harm?

Rgds
R�diger

Last edited by RudiC; 01-17-2018 at 09:40 AM..

RudiC

View Public Profile for RudiC

Find all posts by RudiC

2 More Discussions You Might Find Interesting

1. IP Networking

Identification of data calls & voice calls

Is there any facility to filter/identify the data calls and voice calls coming throug modem? OR Can we get the data or voice calls information through a script(preferably C Kermit)?

2. Windows & DOS: Issues & Discussions

Microsoft Powerpoint 2003 stops working after 12 April 2011 Microsoft Updates

For the benefit of the community this is a widespread worldwide problem affecting multiple versions of Microsoft Windows. Powerpoint erroneously reports Powerpoint presentation damaged and then often hangs. Until Microsoft sort this out, try removing Powerpoint security update KB 2464588...

LEARN ABOUT CENTOS

cups-lpd

cups-lpd(8)							    Apple Inc.							       cups-lpd(8)

NAME

       cups-lpd - receive print jobs and report printer status to lpd clients

SYNOPSIS

       cups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ]

DESCRIPTION

       cups-lpd  is  the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. cups-lpd does
       not act as a standalone network daemon but instead operates as a socket-activatable systemd(1) service.

OPTIONS

       -h hostname[:port]
	    Sets the CUPS server (and port) to use.

       -n
	    Disables reverse address lookups; normally cups-lpd will try to discover the hostname of the client via a reverse DNS lookup.

       -o name=value
	    Inserts options for all print queues. Most often this is used to disable the "l" filter so that remote  print  jobs  are  filtered	as
	    needed  for printing; the examples in the previous section set the "document-format" option to "application/octet-stream" which forces
	    autodetection of the print file format.

PERFORMANCE

       cups-lpd performs well with small numbers of clients and printers. However, since a new process is created for each  connection	and  since
       each  process  must  query  the printing system before each job submission, it does not scale to larger configurations. We highly recommend
       that large configurations use the native IPP support provided by CUPS instead.

SECURITY

       cups-lpd currently does not perform any access control based on the settings in cupsd.conf(5) or in  the  hosts.allow(5)  or  hosts.deny(5)
       files  used  by	TCP  wrappers.	Therefore, running cups-lpd on your server will allow any computer on your network (and perhaps the entire
       Internet) to print to your server.

       You should use configure the firewall to limit TCP port 515 access to only those computers that	should	be  able  to  print  through  your
       server.

       cups-lpd  is  not  enabled  by the standard CUPS distribution.  Please consult with your operating system vendor to determine whether it is
       enabled on your system.

COMPATIBILITY

       cups-lpd does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not  prevent  users  from
       submitting  print  jobs.  While	this  behavior is different than standard Berkeley LPD implementations, it should not affect normal client
       operations.

       The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray	from  this
       definition, remote status reporting to LPD clients may be unreliable.

SEE ALSO

       cups(1), cupsd(8), systemd(1), http://localhost:631/help

COPYRIGHT

       Copyright 2007-2013 by Apple Inc.

4 August 2008							       CUPS							       cups-lpd(8)