All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Bambach <eric@cisu.net>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: root password
Date: Fri, 1 Apr 2005 10:55:44 -0600	[thread overview]
Message-ID: <200504011055.44030.eric@cisu.net> (raw)
In-Reply-To: <5.1.0.14.1.20050330063201.02035bd0@celine>

On Wednesday 30 March 2005 08:36 am, Ray Olszewski wrote:
> Any other suggestion of how to become root without knowing the root
> password is a technique for breaking into systems, and I (and I hope
> everyone else) will not give advice on that publicly, in this forum or
> anywhere else.

I respectfully disagree. How will sysadmins ever know how to secure their 
systems unless they know HOW break-ins occur. Certainly most hacking doesnt 
come from boot CDs but having a more informed sysadmin is infinitely better 
than one that only discovers how to make their system more secure *AFTER* 
being broken into.

What you are saying is that security through obscurity is good and there have 
been countless rebuttals on just how horrible security though obscurity is in 
99% of the situations. The only reason for S.T.O. is a company that found an 
exploit and is giving lead-time to the vendor to patch their vulnerable 
software.

-- 
----------------------------------------
--EB

> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and
a ballistic missile.

                --Alan Cox LKML-December 08,2000 

----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2005-04-01 16:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  7:16 root password Ankit Jain
2005-03-30 14:07 ` Robin Doer
2005-03-30 14:36 ` Ray Olszewski
2005-04-01 16:23   ` Tobias Hirning
2005-04-01 16:52     ` Eric Bambach
2005-04-01 18:03       ` Tobias Hirning
2005-04-02 18:53         ` Ray Olszewski
2005-04-02 19:11           ` Tobias Hirning
2005-04-01 16:55   ` Eric Bambach [this message]
2005-04-01 18:23     ` Ray Olszewski
2005-04-01 23:57       ` J.
2005-04-02  0:56       ` Peter
2005-03-30 16:36 ` Manish Regmi
2005-03-31  0:57   ` terry white
2005-03-31  1:32     ` Jim C. Brown
2005-04-02 12:38 ` Glynn Clements
2005-04-03  3:03   ` Re[2]: root password *reset root password with grub* Kev
2005-04-03  3:04   ` Kev
2005-04-03  3:53     ` joy merwin monteiro
2005-04-04  3:39       ` Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2005-04-03  4:39 root password Ankit Jain
2005-04-03  5:05 ` Jim C. Brown
2005-04-03  5:14 ` Grant Coady
2005-04-04  2:48 ` Glynn Clements
2005-04-04 11:42   ` Andrew
2005-04-04 14:24 ` Scott Taylor
2005-03-30 13:29 Mike Turcotte
2005-03-30 10:31 Rajat  Jain, Noida
2005-03-30  7:48 Wei Zhang GR
1999-08-23  9:06 Root Password Pete Young
1999-08-23 10:15 ` Alistair Lambie
1999-08-21 17:40 William Holmes
1999-08-21 21:19 ` Todd M. Shrider
1999-08-21 22:09   ` brett
1999-08-21 17:27     ` Todd M. Shrider
1999-08-22  2:04 ` Raj Mathur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200504011055.44030.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.