I've just had an interesting and somewhat scary phone call where a
well organised team tried to talk me into giving them access to my
machine. The call started with a woman with what appeared to be an
Indian accent telling me she was from something like the Technical
Support department of Microsoft Windows and asked me a few questions
about the computer. She told me that they had reports that my computer
had been infected which of course is kind of interesting that my Mac
and Linux systems would tell Microsoft that.
Anyway I played along and she said she was going to pass me over to
her supervisor, a man again with an Indian accent apparently, who got
me to get onto the machine and press the key combination 'Windows-r'.
I'm bluffing like mad here while I'm talking and making noises on the
keyboard. He gets me to remove the 'cmd' string from the run box and
enter 'inf'. He then patiently explains to me that the files I can see
there are all the infected viruses and bad things that have been put
on my machine and he's going to help me get rid of them.
So we go back to the run box and type in 'www.teamviewer.com' and then
I fluff about a bit having to connect to the Internet. He offers me
the helpful suggestion that if I'm using wireless I should go to a
"windy place" as that will help it go better. At this point I was
thinking who's got me on the talkback radio setting me up but we
continue and he gets me to type the domain name again. At this point
he goes quiet and appears to be working - but not on my machine I
think. I don't believe I can sustain the bluff any longer and drop the
phone call.
At this point they've been talking to me for 13 minutes so I assume
they think they've really hooked me and they ring back. I fail to
answer and they give up. Using *52 reveals that their number is
....... withheld!
I looked at the URL and teamviewer appears to be a remote desktop app.
These people appear to be pretty happy to spend a longish period of
time on this. They rang our number last week and my wife said they'd
need to talk to me.
Has anyone else seen this?
Want to warn your customers?
________________________________________________________________________
APNIC 32 Conference - Call for Papers
________________________________________________________________________
Hi NZNOG Community,
The APNIC 32 Program Committee is now seeking presentations for the
APNIC 32 Conference to be held at Busan, South Korea from 28 August to 1
September 2011. We are looking for presentations that would suit the
technical conference sessions.
You can submit proposals online and view the key dates at:
http://meetings.apnic.net/32/program/submit
Program Material
----------------
The theme for the APNIC 32 Conference is Destination::IPv6.
The technical sessions at APNIC 32 will include presentations relevant
to Internet operations and technologies and include the following ideas:
- IPv4 exhaustion / IPv6 deployment and operations
- net44[4], 6rd, aplusp
- ISP, Peering, Carrier, and IXP services
- Network security
- Internet policy
- Access and Transport Technologies
- Content and Service Delivery
If you have any another ideas, please feel free to submit your proposal.
If you have any questions, please email the Program Chair at:
pc-chair(a)apnic.net
For more information about APNIC 32, please visit:
http://meetings.apnic.net/32
On behalf of:
Chair: Jonny Martin
Co-chair: Philip Smith
APNIC 32 Program Committee
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS24388:RS-ROUTES:AS38477
descr: advertised to AS24388 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
182.50.160.0/22^22-29,
202.6.116.0/23^23-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
source: NZRR
REPLACED BY:
route-set: AS24388:RS-ROUTES:AS38477
descr: advertised to AS24388 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110607
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110413
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110607
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS38477
descr: advertised to AS9560 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110413
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS38477
descr: advertised to AS9560 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110607
source: NZRR
------------------------------------------------------------
