Philip Prindeville wrote:
The behavior I’ve seen implies that [Thunderbird] caches the address
from the original resolution and keeps trying to reconnect to that.
Well, if it would cache the address for longer than its time to live,
then it would be doing it wrong.
Björn Persson
On 04/21/2015 09:26 AM, Björn Persson wrote:
Philip Prindeville wrote:
The behavior I’ve seen implies that [Thunderbird] caches the address
from the original resolution and keeps trying to reconnect to that.
Well, if it would cache the address for longer than its time to live,
then it would
On Mon, 2015-04-20 at 16:27 -0600, Philip Prindeville wrote:
On Apr 20, 2015, at 12:23 AM, Siddhesh Poyarekar siddh...@redhat.com wrote:
On Sat, Apr 18, 2015 at 01:49:57PM -0600, Philip Prindeville wrote:
If you go back through the previous glibc bugs, you'll find:
On 21.4.2015 16:32, Dan Williams wrote:
On Mon, 2015-04-20 at 16:27 -0600, Philip Prindeville wrote:
On Apr 20, 2015, at 12:23 AM, Siddhesh Poyarekar siddh...@redhat.com wrote:
On Sat, Apr 18, 2015 at 01:49:57PM -0600, Philip Prindeville wrote:
If you go back through the previous glibc bugs,
On Apr 20, 2015, at 12:23 AM, Siddhesh Poyarekar siddh...@redhat.com wrote:
On Sat, Apr 18, 2015 at 01:49:57PM -0600, Philip Prindeville wrote:
If you go back through the previous glibc bugs, you'll find:
https://sourceware.org/bugzilla/show_bug.cgi?id=984
from 2005 which was closed out
On Sat, Apr 18, 2015 at 01:49:57PM -0600, Philip Prindeville wrote:
If you go back through the previous glibc bugs, you'll find:
https://sourceware.org/bugzilla/show_bug.cgi?id=984
from 2005 which was closed out as RESOLVED, WONTFIX with the text:
There is a solution, already
On 04/18/2015 02:25 PM, Björn Persson wrote:
Philip Prindeville wrote:
I recently opened a bug with glibc because persistent programs (like
Thunderbird, etc) don't seem to handle roaming onto different
networks very well.
Or rather, they rely on libresolv which opens /etc/resolv.conf at
Philip Prindeville wrote:
If you're getting bad resolver addresses from your DHCP server,
aren't you also potentially getting a bad default gateway and hence
setting yourself up for a man-in-the-middle attack?
Man-in-the-middle attacks can be carried out from any computer on any
of the
Philip Prindeville wrote:
I recently opened a bug with glibc because persistent programs (like
Thunderbird, etc) don't seem to handle roaming onto different
networks very well.
Or rather, they rely on libresolv which opens /etc/resolv.conf at
startup and then ignores changes to the file for
I recently opened a bug with glibc because persistent programs (like
Thunderbird, etc) don't seem to handle roaming onto different networks very
well.
Or rather, they rely on libresolv which opens /etc/resolv.conf at startup and
then ignores changes to the file for the rest of the time the
On Sat, 18 Apr 2015 21:49:57 +0200, Philip Prindeville wrote:
I recently opened a bug with glibc because persistent programs (like
Thunderbird, etc) don't seem to handle roaming onto different networks very
well.
dnf install bind-chroot, enable it, start it
echo /etc/resolv.conf nameserver
Please see:
https://fedoraproject.org//wiki/Changes/Default_Local_DNS_Resolver
It's an F23 change (deferred from F22).
kevin
pgpUktpQCj8A4.pgp
Description: OpenPGP digital signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
12 matches
Mail list logo
