[Bug 176125] Re: Ubuntu should activate the IPv6 privacy extension by default (echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr)

2011-09-02 Thread UnrealMiniMe
I think the Ubuntu installer should come with a checkbox option:
[ ] Leave me naked on the Internet and STAB ME IN THE BACK.

Regardless of whether it's checked or unchecked by default, I have a
feeling most people aren't going to want that.

Right now, I'm typing on an operating system where Samba defaults to
settings that basically amount to, "Don't let anything work unless the
user manually edits a configuration file," which is presumably for the
sake of security (unless it's for the sake of deliberately hassling
users).  If security is prioritized over functionality, the same should
go for privacy...yet this same operating system freely gives my MAC
address to anyone I bump into with IPv6, because it's more
functional...and get this:  It's not even more functional for ME, but
for hypothetical system/network admins who aren't even using my
computer.  You have to be kidding me.

I cannot BELIEVE the attitude of system admins on this board.  "Oh no,
this will make forensics so much harder..."  Yes, that is the point.
(It's ironic that these comments are positioned so closely to comments
saying that the privacy extensions don't effectively protect privacy.
Obviously, they do so enough to make forensics a pain in the butt, so
they're accomplishing something good at least.)  "It'd be okay if just a
few rogue users used privacy extensions, but when it's set to default
and everybody does it..."  Yes, that is once again the whole point.  To
the extent that it affects me as an end user, "forensics" = tracking,
and it's not something I particularly appreciate.

This may come as a surprise, but end users are not in the business of
serving system admins who want to track them and/or snitch on them when
some copyright mafia comes knocking.  An end user's operating system
should exclusively serve the end user, not others who may have
conflicting interests.  Writing software that obeys and serves the user
[as opposed to potentially adversarial third parties] is such a
cornerstone of free and open source software that the correct course of
action here should be a no-brainer.  Anything else is a betrayal.

Did I mention copyright mafias?  Let's take that up a notch and consider
the ramifications of default "ass hanging in the wind" policies in
totalitarian countries without free speech.  A
journalist/whistleblower/political dissident or such can use encryption,
a VPN, etc. all she wants, but her IPv6 address may be the one weak link
that ultimately ties all of her activity together and betrays her to the
people who want nothing more than to identify, torture, and kill her.
There is simply no excuse for leaving an obscure hole like this open by
default, especially considering that most people are completely unaware
of it.

Are there lots of other ways for people to track you?  Sure.  Browser
fingerprints are a problem, and that problem should be dealt with...but
there are in fact solutions that are being increasingly adopted, and
this problem is restricted to web browsers anyway.  The existence of
such a problem does not justify saying, "Well, let's just give up on
user privacy and broadcast our friggin' MAC addresses to everyone we
bump into, so we can be persistently tracked across any and all
protocols and applications using IPv6."  There are certainly a lot of
bases to cover when it comes to privacy, but sensible defaults go a long
way toward plugging the holes.

Now, if you're a system admin in an actual enterprise environment where
you legitimately have control over a large number of end user PC's (e.g.
employee PC's), then changing the default IPv6 settings should not be an
issue for you...because, after all, you're the one who installed the OS
on all of these computers in the first place, right?  Each one can be
updated with the same modified config file, and this is made even easier
if they're set up as preconfigured virtual machines.  Now, if you're
just a network admin who has no legal or moral right over end users'
computers, it's simply not their job to appease you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/176125

Title:
  Ubuntu should activate the IPv6 privacy extension by default (echo 2
  >/proc/sys/net/ipv6/conf/all/use_tempaddr)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/176125/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 60448] Re: .xsession_errors file grows out of control & saturates disk space

2011-07-18 Thread UnrealMiniMe
I just came across this bug report after finally tracking down my own
disk space issues to .xsession-errors.old.  The file had grown to over
13 GB!

Obviously, most users are not affected by this bug, so it seems to be
triggered by excessive error reporting somewhere else.  In my case, the
most common error is this, repeated over and over and over:

(gnome-power-manager:2073): Gtk-WARNING **: A floating object was finalized. 
This means that someone
called g_object_unref() on an object that had only a floating
reference; the initial floating reference is not owned by anyone
and must be removed with g_object_ref_sink().

I understand that's not really helpful for tracking down the source of
the error, but the redundancy of the errors got me thinking.  At least
on my system (10.10, 64-bit), old errors are occasionally moved from
.xsession-errors to .xsession-errors.old, and the latter file is the one
that soaks up all the disk space.  Others have suggested modifying the
code to prune the logs occasionally.  That should eliminate the problem
entirely, but it hasn't been done.  If there's a reason that cannot be
done, maybe the error redundancy could be exploited using compression?

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in Ubuntu.
https://bugs.launchpad.net/bugs/60448

Title:
  .xsession_errors file grows out of control & saturates disk space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/60448/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs