On 06/03/12 17:50, Camaleón wrote:
In brief, I think the default is a very limited setup. Let's not be
paranoids :-)
I dont think im being paranoid. I thought debian was about doing things
right, no matter the time it takes... :)
This is my follow-up to this topic:
On Tue, 13 Mar 2012 11:35:54 +0100, Alberto Fuentes wrote:
On 06/03/12 17:50, Camaleón wrote:
In brief, I think the default is a very limited setup. Let's not be
paranoids :-)
I dont think im being paranoid. I thought debian was about doing things
right, no matter the time it takes... :)
On Tue, Mar 06, 2012 at 04:05:03PM +0200, Mika Suomalainen wrote:
You seem to be ignoring the third part of that email.
I wasn't, that part missed the point, but since you've sent this
to -user 8 times so far I might as well bite and reply. (Please
stop!)
There's no need for ntpd to listen for
On Tue, Mar 13, 2012 at 01:07:39PM +, Camaleón wrote:
For instance, I wouldn't see any objection in splitting the package in
the same way sshd is (there is a client and a server part) and set
the desired configuration (as server or client) for each of them.
I would. The answer to people
On Tue, 13 Mar 2012 14:42:12 +, Jon Dowland wrote:
On Tue, Mar 13, 2012 at 01:07:39PM +, Camaleón wrote:
For instance, I wouldn't see any objection in splitting the package in
the same way sshd is (there is a client and a server part) and set
the desired configuration (as server or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Him
I am sorry about that spamming. I apologized in separate thread (
http://lists.debian.org/debian-user/2012/03/msg00447.html ), but you
probably missed it.
On 13.03.2012 16:40, Jon Dowland wrote:
On Tue, Mar 06, 2012 at 04:05:03PM +0200, Mika
On 05/03/12 22:35, Jon Dowland wrote:
On Mon, Mar 05, 2012 at 12:38:52PM -0700, Bob Proulx wrote:
The entire purpose of ntp is to interact on the network. Not doing
this would be similar to installing sshd and then wanting it not to
listen to the network. That would severely reduce its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
Jon, how would you listen only LAN by default? There are multiple
different router types and manufactors and not all of them share
the same IP range. And there are also people who run ntp on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You seem to be ignoring the third part of that email.
On 05.03.2012 23:35, Jon Dowland wrote:
- --
Mika Suomalainen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
On Mon, 05 Mar 2012 15:20:05 +0100, Alberto Fuentes wrote:
I think /usr/share/doc/ntp/README.Debian.gz is bad worded. Correct me if
im wrong but it says [...]The default ntp.conf file is set up for an
NTP client that [...] [...]Extra configuration work will be
necessary to offer time service
On 06/03/12 15:34, Camaleón wrote:
On Mon, 05 Mar 2012 15:20:05 +0100, Alberto Fuentes wrote:
I think /usr/share/doc/ntp/README.Debian.gz is bad worded. Correct me if
im wrong but it says [...]The default ntp.conf file is set up for an
NTP client that [...] [...]Extra configuration work will
On Tue, 06 Mar 2012 16:32:03 +0100, Alberto Fuentes wrote:
On 06/03/12 15:34, Camaleón wrote:
On Mon, 05 Mar 2012 15:20:05 +0100, Alberto Fuentes wrote:
I think /usr/share/doc/ntp/README.Debian.gz is bad worded. Correct me
if im wrong but it says [...]The default ntp.conf file is set up for
I think /usr/share/doc/ntp/README.Debian.gz is bad worded. Correct me if
im wrong but it says [...]The default ntp.conf file is set up for an
NTP client that [...] [...]Extra configuration work will be
necessary to offer time service to other hosts. [...]
By default, it works as a server not
On Mon, Mar 05, 2012 at 03:20:05PM +0100, Alberto Fuentes wrote:
I think /usr/share/doc/ntp/README.Debian.gz is bad worded. Correct
me if im wrong but it says [...]The default ntp.conf file is set up
for an NTP client that [...] [...]Extra configuration work will
be necessary to offer time
Jon Dowland writes:
Wow, good point. Indeed it *does* appear to be listening as a server
for other clients, by default, and I'd agree this is perhaps not the
best default.
As long as it listens only on the LAN I don't agree.
--
John Hasler
--
To UNSUBSCRIBE, email to
On 05/03/12 18:26, John Hasler wrote:
Jon Dowland writes:
Wow, good point. Indeed it *does* appear to be listening as a server
for other clients, by default, and I'd agree this is perhaps not the
best default.
As long as it listens only on the LAN I don't agree.
well, it does not. It
Alberto Fuentes wrote:
John Hasler wrote:
Jon Dowland writes:
Wow, good point. Indeed it *does* appear to be listening as a server
for other clients, by default, and I'd agree this is perhaps not the
best default.
As long as it listens only on the LAN I don't agree.
well, it does not.
Bob Proulx writes:
The entire purpose of ntp is to interact on the network. Not doing
this would be similar to installing sshd and then wanting it not to
listen to the network. That would severely reduce its usefulness. If
you install ntp then there is an expectation that it will behave
I wrote:
Ntp should listen on the LAN by default but there is no reason for it
to listen on the LAN by default.
Should read Ntp should listen on the LAN by default but there is no
reason for it to listen on the _WAN_ by default.
--
John Hasler
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I agree with Bob, that ntp should interact with the network.
Also,aren't most of people using firewalls anyway?
John, how would you listen only LAN by default? There are multiple different
router types and manufactors and not all of them
John Hasler wrote:
Ntp should listen on the LAN by default but there is no reason for
it to listen on the _WAN_ by default.
But the difference between those two things depends upon how the
network is configured outside of the local host machine. In other
words, how is the local host machine to
On Mon, Mar 05, 2012 at 12:38:52PM -0700, Bob Proulx wrote:
The entire purpose of ntp is to interact on the network. Not doing
this would be similar to installing sshd and then wanting it not to
listen to the network. That would severely reduce its usefulness. If
you install ntp then there
On Mon, Mar 05, 2012 at 10:30:28PM +0200, Mika Suomalainen wrote:
Also,aren't most of people using firewalls anyway?
Defence in depth.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This might be a little offtopic, but Ubuntu is also allowing NTP to be accessed
outside localhost by default too.
Mika Suomalainen
gpg --keyserver keyserver.ubuntu.com --recv-keys 62FE66853913CB03
-BEGIN PGP SIGNATURE-
Version: APG v1.0.8
30 matches
Mail list logo
