Password policy changes
by Adam Williamson
Hey, folks. I'm writing with my Server SIG member hat on, here. We've
been discussing password policy changes at our meeting today.
So the Great Password Policy Bunfight of 2015 was resolved by anaconda
creating a mechanism for products/spins to set their own password
policy:
https://github.com/rhinstaller/anaconda/commit/8f24eeaedd7691b6ebe119592e...
I'm slightly worried, however, about the possibility that everyone
goes out and picks a more lenient policy more or less at random and we
wind up with different policies on every Fedora medium. That seems
like it'd be needlessly confusing to users and difficult to document.
I'm wondering if those products/spins intending to set a policy weaker
than the default could all agree on the same one, so there'd only be
at most two policies to care about (and if all products/spins overrode
the upstream default, there'd only be one).
The obvious choice would be the pre-F22 policy, which I believe should
be:
--nostrict --minlen=6 --minquality=50 --nochanges --emptyok
(though it's not *entirely* clear from the code - I think it used
pwquality upstream defaults - so I may be a bit off).
What's the general feeling here? Have other SIGs discussed this yet?
Come to any decisions? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years
User doesn't get a fully localized system
by Jiri Eischmann
Hi,
what I hit everytime I install Fedora Workstation localized to Czech is that after installation from live ISO the system is not fully localized. It's understandable that we cannot fit full support for every language into the Workstation live ISO, but we should have a mechanism that will download all necessary packages after system installation. Something that does the same job as 'dnf langinstall'. The problem with dnf-langpacks is that it's not installed by default and it's a pretty bad user experience if you require the user to go to the terminal to get what they ultimately want: a fully localized system. IMHO it's something that should be done automatically.
By running 'dnf langinstall cs' I got this list of packages:
autocorr-cs
gnome-getting-started-docs-cs
hyphen-cs
libreoffice-langpack-cs
man-pages-cs
mythes-cs
It means the user doesn't have localized LibreOffice, doesn't have autocorrection in their preferred language, and even Getting started which should explain them basics of using the system is not in their language of choice.
Any ideas how to solve this?
Jiri
9 years
need help compiling vte from source
by kendell clark
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
hi all.
I've been trying for a while to compile vte from source in fedora, in
order to test accessibility issues fixed in the following bug:
https://bugzilla.gnome.org/show_bug.cgi?id=746488. However, when I try
to run ./configure, i get the following errors, which I can't seem to
get around. Checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for VTE... no
configure: error: Package requirements (glib-2.0 >= 2.40.0 gobject-2.0
pango >= 1.22.0 gtk+-3.0 >= 3.8.0 gobject-2.0 gio-2.0 gio-unix-2.0
zlib gnutls >= 3.2.0) were not met:
No package 'gnutls' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables VTE_CFLAGS
and VTE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I've run the following to try to resolve. Yum-builddep vte3, it
returns that I have all necessary packages installed. Looking at this
it looks like it can't find gnutls. I've checked yum info gnutls, and
my version is newer than 3.2. I've also done a yum reinstall gnutls
just to make sure something wasn't messed up somewhere, to no avail.
I've seen one other package claim it can't find gnutls, and that is
tintin, the mud client. Anyone have any ideas? I eventually want to
build an rpm of vte 0.39.92, but that won't work if I can't build from
source. Sorry for the newbie questions, but I'm new to fedora, having
just switched two weeks ago. Also, if I'm not supposed to paste in
emails and use fpaste instead, please let me know and I'll use that
from now on. I'm not trying to flood the list
Thanks for reading
Kendell clark
Sent from Fedora GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVEfcHAAoJEGYgJ5/kqBTduJcP/21vMULdy4lL9HIxl4xAy/uR
GMjxFOW4DR4VZzERwPqmVROA4Kq+l3+Fy+7UoxFm6yj03zdGczgDcv0O7WXZJMDs
cWAXhpf6UIYgR0fmVPgtxQuh4X2cBV2No+s04W2vN4zaMIfFi44V0Pm5wBcjuc1w
zvKRwdrl6SeWytHWBNrczkhaYYoTIE2azuECbe0FmujdyVZKTyARXnfOPGKvScYr
AI9oKVqCBPS0Y7jkCpIg2H+AGx0u0PRxDf0jZ92D7kJYVE9W/Gbo9ja16m1w46I3
ovQo+GRKRFk0B44ytxBUSDwEkbu1Tc9FavXCMf43P3nKhM/vKCPs1soLzLPoWxF2
wYu1VA+USnM4bb41/RafL7PCek86+0OErtkiRWkj8L/08oi0tXvLim6XhE7ERF4M
5UYqyvZqEJkEt4qDplGrLAKJGmNl9Y45S0UeZZ88/paTVmQFuu/MC6Gp1EOd0zic
4uLQ7T+Dtv0yRVeKHeiMVDNgwVto1xPclZa19KoXmftwCSHMEU/j+Kb6ntXFRyGX
7NaolLz8Dqe6WmLND9f9wt9STODhCvGVZx4zVSeD65xLdeAHb8+UwIF2bNml3Dsd
Xz0z7VkMkGsu8IjQxFSkGFEo4qY9SbI8Ap1fz7RsXuKaBhaUa5nkCjpJjrtKaDws
JalUbhs5Fmv0Hm3qyTGV
=rwBU
-----END PGP SIGNATURE-----
9 years
plan: fix all remaining accessibility issues for gnome 3.18
by kendell clark
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
hi all.
I'm writing in to let everyone on the desktop list know that I'm
intending to work with anyone here and with the gnome people to fix
all remaining accessibility issues for gnome 3.18. This currently
includes, unlabeled controlls, buttons and links, in various gnome
control center modules. Duplicate controlls in the power settings
module, duplicate buttons in gnome tweak tool. Gdm is inaccessible to
orca. Orca is unable to see the login screen so cannot navigate it's
controlls. This last one is exclusive to gnome 3.16, gnome 3.14 works
just fine. I plan to have all these issues ironed out in time for
gnome 3.18 and f23. I will file bugs, provide logs, anything that is
necessary. My plan is that by f23, there will be 0 (zero)
accessibility issues with orca and gnome shell. I would like to make
one possible request, not sure where this is applicable. Would it be
possible, as a temporary measure, to cause gdm to fall back to using x
for it's login screen when accessibility is enabled? I have no idea
how this can be done, but this would allow orca to again see the
screen and navigate it, until whatever is wrong in wayland can be
fixed up stream? If there are any people who work on gnome itself,
would you mind logging on to #fedora-accessibility, or I can log on to
#a11y on gnome's server to discuss issues? I don't want to flood the
list with accessibility traphic.
Thanks
Kendell clark
Sent from Fedora GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVD2P9AAoJEGYgJ5/kqBTdoCkP/29oOPh23a2K4R/PfOoOZTan
pc194D7gvzU2wEQsXp240AtLSd/62/p5btddEtyR59QkhQHXoyYCQQ36dMqc6rYW
A+Lq9tE8P/H9IuZASf3JS86TCq2k0PKh4HufA2E/3x5NjRJ0nguiYp4HPzmux/kv
ql6KVgvbrBoHz4kj7CV+Qg+Jq1lgDhXZlo7aidNaL/DELzQeYNWnkrSN0XhX1Uqq
6Qenvp47Hg2CvFfAhzb302YxMBXfHhtJkvjXZ8wkgWmAJEppisI2/3McUXHXjRdt
EG8J77zHgsEqdgC7MZFPmhOUE/RI/5FkBix9bQKA5OgxxeDkHGINyuhwj5AlHLq1
Cx4cuFzgNVI/kv8n8eRQuYl1sLe4I/eoM59v1ETsihz1O+PYOHgompYOVWUEqmgn
KFce/Db2gxJKXRghHra7ZVaQnz8+EYvLs8xu+nF+NFVYD+gGqGbwJcIrrLBBu5JT
ylcQ8zf0TYjm+M1NeLJrhmeQav5SUj+Hq9D9T6uZMj5NmZQXx+wKXNUjFsC0CXWh
xEH9ywHAWiwrcqKmpCAnXaQKQViI4uLRXh2HHfwEBGkU0PTvNcReVGiRfQbGNkp4
12W8UskCfucmx14wIChPVd5/qSme/sRTC6yK2YpcJieAoXyaNU6fu4aQ1Fweg2Ob
lgAv4RnTDn0fmmFs0f6C
=955T
-----END PGP SIGNATURE-----
9 years
frustrated with the state of linux accessibility
by kendell clark
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
hi all
I'll warn you all now before I start, this is going to be a bit of a
rant. If you don't have the time to read this, please skip. Before I
rant, I want to make this crystal clear that I am *not* aiming this at
fedora. You guys have been incredibly helpful and you seem to really
care about accessibility. <Beginning of rant>
I am, to put it bluntly, completely exasperated with the state of
linux accessibility, and the amount of work that seems to be needed
just to keep accessibility functional, let alone surpassing that of
other operating systems. I switched to linux over 3 years ago, and was
immediately impressed. Within five minutes, I'd wiped off windows and
replaced it with linux. Orca immediately came up talking, I could
install independently, all the apps were accessible, etc. I quickly
ran into the same wall I've been trying to tear down these past 3
years though. When an app fails to be accessible, the fun begins.
First, I'm directed to contact the app developer, usually via mailing
list or irc channel, so I do so. Hi, I'm blind, and I want to use
application x. Unfortunately it has accessibility issues with orca. It
won't "whatever is wrong with the app". Is there anything I can do to
help you fix it? I wait for a response. "go away you blind idiot, I
don't have time to fix accessibility issues. Use windows, it just
works". That's not the response most of the times but it boils down to
this. The response is usually something like "Unfortunately no one on
our team knows about accessibility. Accessibility in linux is
incredibly difficult. Maybe you could try our app in windows, it'll
probably work there." This, to put it bluntly, does not solve my
issue. I'm using linux because I do not want windows, and being told
to go back there just frustrates me. Dejected, I log off of the irc
channel and go to the orca list. Hi. Does anyone have experience with
application X? I'm trying to use it with orca version "orca version"
and it "whatever's wrong with the app. "Can anyone help with a
workaround, or can I provide any info to help?" I get a response back
from joanie, who's the orca maintainer. Provide me with a debug file.
Ok, fine, I do that. SHe looks at it, eventually. SHe either fixes it
in orca, which she's really good at by the way or ... "well I can't
fix this. It's a bug in such and such. You'll have to file a bug." Ok,
so I go find their bugzilla page, and file a bug. If it's a framework,
such as at-spi, I don't even bother filing a bug because I don't know
enough to gather debug info at-spi needs, so I'd just be complaining
"this doesn't work" which won't help anyone. My main problem is this.
I'm tired of being overlooked. I do what I'm supposed to in an open
source project to get bugs fixed. I file a bug. I go on mailing lists
and send emails describing issues I'm having. And the only responses I
tend to get are, "No one knows anything, sorry." "accessibility is
complicated, use windows." "We're too understaffed and we'll get
around to it eventually." What am I doing wrong? You sighted people
have no idea how lucky you have it. You can pick up any product off
the shelf and immediately use it. We have to have so many
prerequisites to be in place before we can even think of using
something, most of the time aren't in place, so we can't use it. Why?
Why is accessibility such an uphill battle. Why do I file bugs, only
to have them sit for months, or years before they're fixed, if they're
fixed at all? All I want is to be equal with the people who don't need
a screen reader to use their computer. If I file a bug, it gets fixed.
I don't want special treatment. I just want accessibility to work, and
to keep working. It so often does not happen. Accessibility gets
broken far too easily, no one knows what broke it, and it stays
broken. So many desktops I cannot use. Kde, xfce, lxde, lxqt,
cinnamon. So many applications I cannot use. Chrome/chromium,
applications written for x, rather than using a gui toolkit like gtk
or qt, applications that use something other than gtk or qt for their
toolkit. I've used alternative platforms, like windows, It *is* not
perfect. It has it's own issues. But the desktop, most of it at least,
works, and works well. No unlabeled controlls, no duplicate controlls,
etc. Applications are another story altogether. Gnome has trouble even
keeping their own login manager accessible, to say nothing of other
dm's, kdm, lightdm, etc. What am I doing wrong? I want linux to be a
no brainer for blind people all over the world to use. Most of them
are downright spoiled and hostile to having to put forth any kind of
effort, so that cannot happen until and unless accessibility is taken
as seriously as user interface design and marketing. Please help me
understand. Am I so insignificant that developers just can't be
bothered helping a blind person use their app, when they can be lazy
and a thousand, a million sighted people can, so what's the point for
a few blind people? Is that it? I cannot even turn to blind agencies
to help me, as distasteful as that sounds to me, because the vast
majority of them seem to have been bought off by microsoft or apple.
I'm so tired of the "use windows, it just works. Linux'll never get
anywhere." or the , "Just use mac, it's all I need, and it's
completely accessible." from other blind people when I try to get
interest in fixing linux accessibility issues. I'm a nice person, up
to a point. I'm willing to work with developers who are willing to fix
their accessibility issues. But I'm not as patient as I once was. Too
many times I've been promised accessibility fixes, only to get
nothing. The excuses don't matter if you don't keep your word. It
comes to a point when I just want to log onto an irc channel and yell,
"ok, there's yet another accessible issue. Someone get on this
immediately and fix it or I'll ..." I don't, because that's going to
get me nowhere, as well as banned. But I'm tired of running in
circles. It's not our problem, go bug these people, it's their toolkit
that's keeping orca from reading the app. It's so complex I have only
the vaguest understanding of how the tools fit together in order for
orca to read my screen. <end of rant> Ok, that felt good. I've talked
long enough, so I'll end this. Please don't ban me, like I said in the
beginning this is not fedora's fault. You people have shown that you
care about accessibility, and I've seen proof in your tools. They're
all accessible. This rant is *not* directed at you. But linux
accessibility needs a kick in the pants. It needs a big company with
lots of money behind it, rather than a handful of developers fixing
the issues, in their spair time. I don't know how many blind linux
users their are but reguardless of the number, they deserve the same
experience a sighted user gets when they turn on their computer. I
will do whatever it takes to fix this, if it takes dedicating the rest
of my life to this. I don't have much money to spair, but I can
probably donate some, if money is needed. I picked fedora because it's
backed by redhat, and because the community is caring and helpful. I
need help. What do you long time and sighted linux users think can be
done about this? I'm tired of the disinterest from developers, the
assumption that surely there's another app that I can use, so they
don't have to bother fixing accessibility issues. Surely I can switch
to another platform, usually windows, because linux isn't cut out for
what I want to use it for. That's clearly false, time and time again
with effort it can quickly surpass other platforms. But so often that
effort isn't even started. Or started and abandoned. Google won't even
make chrome accessible using pre existing accessibility frameworks.
At-spi on linux, something else on windows I forget the name. Instead
they develop their own, completely nonstandard and possibly closed
source implementation, and expect you to use that if you want to use
their browser. Duplication of effort is not the answer. I personally
think, and I could be completely wrong, but I think there needs to be
an accessibility standard framework that applications adhere to. This
is already here, in terms of at-spi2. This needs to be baked into the
display server itself, so that applications either cannot, or cannot
easily render their applications inaccessible. Otherwise we're going
to have the same situation we're struggling with today. Accessibility
problem, file bug, wait. It may or may not get fixed. This *needs* to
get fixed and stay fixed. I want to help that happen, not whine and
complain. I realize I've just done that, but this will be the only
email of this kind you'll get from me. I just had to get it out there
for people who have moer experience with linux than I do to chew on.
Please don't ban me, I want to help fedora, and by extension all linux
distros get better in terms of accessibility.
Thanks for reading
Kendell clark
Sent from fedora GNU/Linux version 21
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJVCMpnAAoJEGYgJ5/kqBTdAlkP/1oF1e1wNvAV9oo5bIUbHkBt
uwAggXbKz2uQwfA02y84o5XDmsGBjn7w06vBz+3GIP5a4Qh9GRvxZfJY/kz04XW4
CpSmH7a97p/pUGR8V51WtYeq+T6fMi0ppcXjLbj0XUDqjXm2htxx6ipg4pw5PG3Q
pp2wP1KBYhb0+/pwIxgaE/f2PXburqJYCTg/st+upXkTWDeuBhHfCtQ0cguiKJlW
nnoPUjczO52G8JBOxuh+l93FoI6ZlWLmVO/gx0PbbE7SUguXleTPv5pnbMBrMVSy
9HTQNjD/lms21hydKGQokXfgdAPtLzdjtCAIW6sTQeo+PpB9q+QcrjxGiOGWqBhP
iGMAzDf+MvpVw9a4gM3bNstcHJtZcoG61fjclSpJzqS5uYhahNPwbgcOIpyT61pV
VqWawkrxGkMDmojZHbSogR3i7cJEo/qU/MMbvT76RPdnXmvhmBTDx+ZgRa9lC7o8
e8BvIpDFnGg8IiKZziwgh8Sl1qSk3S6ZllUHMbVWc9tAeTCrKlMxtpRlvWhUQKPB
8K/TeTvS14j1hxHrGmPltUNBGczvEKjkM46b8yFUBEmPLOWo89TgcE6sFtc0ah+t
/QJvt6bq67fr8WcJI/TGvGUu60JiqsK9GMs8SFd//U0kE42JlPf9LO2EhKIX1azG
ZcOC6Kh+jouhp4bB7vaB
=uj+2
-----END PGP SIGNATURE-----
9 years
GDM Shield
by Adam Batkin
Is it possible to get rid of the shield on the GDM login screen (even if
it's a hidden option somewhere)? It's really annoying to have to drag it
out of the way or hit a specific key on the keyboard to dismiss it. And
considering the behavior of other operating systems, as well as the
history of Linux software, I don't think it's unreasonable to desire the
ability to get rid of it.
I've seen https://bugzilla.gnome.org/show_bug.cgi?id=696330 but I'm not
sure if it's the same shield (also, no one seems to take an interest in
working on that bug). Although I'd suggest that the issue also be
handled in the general Gnome screensaver usage too, that at least
doesn't affect me anymore since KDE does its own thing when it comes to
screensavers.
Thanks,
-Adam Batkin
9 years