$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk? Security through obscurity? Really? In this
day and age?
Or am I missing something
On Dec 18, 2012, at 1:01 PM, Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk? Security through obscurity? Really
On Tue, 18 Dec 2012 21:01:33 + (UTC), Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk? Security through obscurity
On Tue, Dec 18, 2012 at 3:01 PM, Walter Hurry walterhu...@gmail.com wrote:
Security through obscurity? Really? In this
day and age?
My password is obscured from you. I consider that more secure regardless
of what any other opinion is.
--
Adam Vande More
On Tue, 18 Dec 2012 21:01:33 + (UTC)
Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk? Security through obscurity
On 12/18/12 22:32, RW wrote:
On Tue, 18 Dec 2012 21:01:33 + (UTC)
Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk
On Tue, 18 Dec 2012 21:32:50 +, RW wrote:
On Tue, 18 Dec 2012 21:01:33 + (UTC)
Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk
On Tue, Dec 18, 2012 at 10:01 PM, Walter Hurry walterhu...@gmail.com wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why is it a security risk? Security through
On 12/18/12 23:04, C. P. Ghost wrote:
On Tue, Dec 18, 2012 at 10:01 PM, Walter Hurry walterhu...@gmail.com wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why
On Tue, 18 Dec 2012 22:53:29 +0100
Polytropon wrote:
On Tue, 18 Dec 2012 21:32:50 +, RW wrote:
On Tue, 18 Dec 2012 21:01:33 + (UTC)
Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your
On 12/18/12 23:44, RW wrote:
On Tue, 18 Dec 2012 22:53:29 +0100
Polytropon wrote:
On Tue, 18 Dec 2012 21:32:50 +, RW wrote:
On Tue, 18 Dec 2012 21:01:33 + (UTC)
Walter Hurry wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all
On 12/18/12 23:04, C. P. Ghost wrote:
On Tue, Dec 18, 2012 at 10:01 PM, Walter Hurry walterhu...@gmail.com wrote:
$ sudo /usr/libexec/locate.updatedb
WARNING
Executing updatedb as root. This WILL reveal all filenames
on your machine to all login users, which is a security risk.
$
Why
You have paths that are over 1024 characters long.
Tell updatedb not to use them (/etc/locate.rc exists for this).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
Running 6.1 fresh install one of my routines after installing is
updating the locate database but I am getting errors and it is not
fulling updating.
locate: integer out of +-MAXPATHLEN (1024): 1027
locate: integer out of +-MAXPATHLEN (1024): 1027
14 matches
Mail list logo