Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.networking > #3875

Re: What should I change my DNS to? (combined response)

From Moe Trin <ibuprofin@painkiller.example.tld.invalid>
Newsgroups comp.os.linux.networking
Subject Re: What should I change my DNS to? (combined response)
Date 2016-09-07 21:50 +0000
Organization This mind intentionally left blank.
Message-ID <slrnnt12st.mar.ibuprofin@planck.phx.az.us> (permalink)
References (4 earlier) <nqlslb$2ct$1@gioia.aioe.org> <slrnnsudm2.aik.ibuprofin@planck.phx.az.us> <nqnt4b$1e46$1@gioia.aioe.org> <slrnnsvee9.i3b.ibuprofin@planck.phx.az.us> <nqofhm$476$1@gioia.aioe.org>

Show all headers | View raw


On Wed, 7 Sep 2016, in the Usenet newsgroup comp.os.linux.networking, in article
<nqofhm$476$1@gioia.aioe.org>, F Volker wrote:

>> See my reply to Carlos

>Yes, I had a look at it - woosh, it went right over my head. I am just 
>not good following this technical stuff.

They're no longer maintained, and therefore rarely included in Linux
distributions any more, but there is a large amount of technical
information for the less-skilled still available. They were called
"HOWTO"s and in the late 1990s there were about 500 documents, such as
the DNS-HOWTO:

     * DNS HOWTO
       Updated: Dec 2001. How to become a totally "small time" DNS
       admin.

which is about 40 pages long.   A bit dated, but still useful:

     * The Linux Networking Overview HOWTO
       Updated: Jul 2000. Overview of the networking capabilities of the
       Linux Operating System; provides pointers for further information
       and implementation details.
     * NET3-4-HOWTO, Linux Networking HOWTO
       Updated: Aug 1999. Aims to describe how to install and configure
       the Linux networking software and associated tools.

>So, the staff of the ISP are able to by-pass my Gateway username & 
>password of the router and can reset the router settings even though
>the 'remote management' function is disabled; I am astonished!

They MAY be able to do so - it depends on the specific manufacturer and
model.

>The settings are supposed to protect my privacy - if they are for nought 
>what is there left to do especially for a non-tech person?

Yes, that is a continuing problem.

>Don't the manufactures of reputable routers know that these settings can 
>be so easily compromised? Right now I feel cheated.

Ever wonder how long it's been ``normal'' for a manufacturer to include
a password protected account that is accessible from the world?

You've got to feel sorry for the {computer|modem|router} manufacturers.
They have to provide a complicated piece of electronics to the public,
and yet these devices have to be configured for such things as IP
address, address ranges (network mask), gateways, and the like, and
to have the average user do this is inviting disaster.  Everyone KNOWS
that the user will not read the instruction book (why should they,
when the book if full of warnings about operating the system in the
bath tub, not trying to clean it with gasoline and a hair dryer, or
letting children play with the plastic bag it came in, and similar
typical user errors expected by the company lawyers).  So it's got to
be really simple - because the users have absolutely no intention of
learning anything.  Hey, they know how to live without someone standing
next to them saying "Breath in...  Breath out..." 24 hours a day.

The manufacturer also KNOWS that the owner/user is going to screw up the
configuration of the box.  What can they do?   It's far to expensive to
have a technician come out to the house to configure things correctly,
and in any case the customer is going to be whining about having to be
home when the tech comes - which screws up scheduling and increases
costs yet again.

So they give the product a remote access, which allows them to fix the
configuration errors remotely.  But they've sold (or hope to sell)
thousands of these boxes. Should they have a unique password for each
and every one?   Not possible.  How would they know which one is
which?  Ask the customer to read a serial number?  Can't do that, as
the customer will whine about invading their privacy, never mind not
knowing how to read the numbers off the tag on the back or bottom of
the unit.   Well, I guess we'll have to have one password for
everyone...   wonder what that password will be...  something hard to
guess (one would hope)...  I know!  How about "admin"?  The partially
trained drug-crazed chimpanzees we've hired as customer service
representatives (at a pay rate of 2 bananas a day) should be able to
remember that one even if it's not a word in their native language.

You think I'm joking.  Surely the manufacturers would choose a much
obscure password (and username).  Why, that's as st00pid as the
passwords chosen for the administrator account on a windows box, by
users who lack the intelligence of retarded duck.  Remember the
W32/Deloader worm from March 2003?  (If not, use your favorite search
engine (try CERT Advisory CA-2003-08) and find the 87 passwords it knew
would work. Is your current password included in that list?)  And it's
getting worse, because of the "Internet of Things" - where modern
products like your refrigerator and cook-stove are going to have
Internet connectivity so that they can talk to each other and decide
what you are going to eat tonight (to improve your living experience,
what-ever that is supposed to mean).  Doing an internet search for
"default password list" should turn up lists of the secret passwords for
many products, and you'd be horrified to see how many use "admin" and
"admin" in spite of this problem being well known for more than 30 years.

So they should include instructions in the manual (that no one is going
to read) instructing the customer to _change_ the password.  Right, we
know how often that is going to work.  Besides, the "new" password is
_still_ going to be one of those 87 used by the W32/Deloader worm, and
in any case, the customer will have forgotten the damn thing anyway.
Put a "reset" button on the device, that the customer can press to
restore the system to factory defaults?  Bad idea, as this will
increase the cost, and unless it's physically out of the way will be
pressed accidentally or on purpose by the children of that retarded
duck.  And in the factory default mode, it doesn't work the way the
customer expects, so you must be selling plastic powdered dog p00p
(instead of the high quality real dog poop the customer expected and
paid for.)   The manufacturer get's blamed no matter what.

        Old guy

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 06:32 +0700
  Re: What should I change my DNS to? Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-06 03:35 +0000
    Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 13:48 +0700
      Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-06 07:25 +0000
        Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-06 14:53 +0700
          Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 09:40 +0000
          Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-06 10:35 +0000
            Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 11:09 +0000
            Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 08:53 +0700
              Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-07 08:24 +0000
                Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:02 +0200
                Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-08 06:42 +0700
                Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 03:10 +0200
                Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-08 09:43 +0700
          Re: What should I change my DNS to?  (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-06 21:36 +0000
            Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 00:48 +0200
              Re: What should I change my DNS to? (combined response) William Unruh <unruh@invalid.ca> - 2016-09-07 08:18 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:08 +0200
                Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 21:52 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 00:52 +0200
            Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 09:13 +0700
              Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 04:26 +0200
                Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 09:41 +0700
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:11 +0200
                Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 10:59 +0700
                Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 06:53 +0000
                Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-07 11:02 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:21 +0200
                Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-07 14:09 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 21:53 +0200
                Re: What should I change my DNS to? (combined response) Dan Purgert <dan@djph.net> - 2016-09-08 11:06 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-08 15:22 +0200
              Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 06:55 +0000
                Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-07 14:27 +0700
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-07 14:28 +0200
                Re: What should I change my DNS to? (combined response) Stefan Monnier <monnier@iro.umontreal.ca> - 2016-09-07 09:32 -0400
                Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 21:50 +0000
              Re: What should I change my DNS to? (combined response) William Unruh <unruh@invalid.ca> - 2016-09-07 08:29 +0000
            Re: What should I change my DNS to? (combined response) F Volker <here@home.net> - 2016-09-08 10:15 +0700
              Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-08 19:34 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-09 03:56 +0200
                Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-09 20:55 +0000
                Re: What should I change my DNS to? (combined response) "Carlos E. R." <robin_listas@invalid.es> - 2016-09-10 02:47 +0200
                Re: What should I change my DNS to? (combined response) Bit Twister <BitTwister@mouse-potato.com> - 2016-09-10 08:27 +0000
                Re: What should I change my DNS to? (combined response) Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-10 22:53 +0000
      Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 13:35 +0200
        Re: What should I change my DNS to? Aragorn <thorongil@telenet.be.invalid> - 2016-09-06 14:06 +0200
          Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 14:27 +0200
            Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 13:03 +0000
              Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 17:01 +0200
                Re: What should I change my DNS to? Dan Purgert <dan@djph.net> - 2016-09-06 16:25 +0000
                Re: What should I change my DNS to? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-09-06 21:37 +0300
                Re: What should I change my DNS to? "Carlos E. R." <robin_listas@invalid.es> - 2016-09-06 23:42 +0200
        Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 09:26 +0700
      Re: What should I change my DNS to? Roger Blake <rogblake@iname.invalid> - 2016-09-06 12:54 +0000
        Re: What should I change my DNS to? F Volker <here@home.net> - 2016-09-07 09:28 +0700
          Re: What should I change my DNS to? William Unruh <unruh@invalid.ca> - 2016-09-07 08:25 +0000
        Re: What should I change my DNS to? Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2016-09-07 03:29 +0000

csiph-web