Public bug reported:
Dear Colleagues,
ipa-client-install fails at the import stage of the freeipa server cert.
Created /etc/ipa/default.conf
New SSSD config will be created.
Configured /etc/sssd/sssd.conf
Traceback (most recent call last):
File "/usr/sbin/ipa-client-install", line 1292, in
Well
this patch is not the right location.
We should create this directory in debian/rules
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1024765
Title:
ipa-client-install failes at certutil
Public bug reported:
Dear Colleagues,
the chkconfig call in add_debian.py.patch doesn't work on Ubuntu (didn't test
it with Debian though), because /sbin/insserv doesn't exist.
/usr/lin/insserv/insserv exists, but doesn't behave correctly.
For Ubuntu we should rewrite these calls, to match our
Public bug reported:
Dear Colleagues,
the package 'dbus' is missing during package installation of freeipa-client
package.
Even when 'libdbus-1-3' is a binary dep of certmonger package, and libdbus-1-3
refers to the dbus package as recommended binary dep, it won't be installed by
default.
Wi
Timo & Stephen,
yes, but not when you have Recommends turned off, which is quite usual on
servers in datacenter environments.
So, I have a debootstrap / minimal installation for our servers. Recommends
are turned off for apt-get/aptitude.
libdbus-1-3 gets installed, but only recommends the db
The attached branch has the right bugfix.
I tested in on my local installations and it works like a charm.
Certutil call of ipa-client-install won't fail anymore on this missing
directory.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa
Public bug reported:
Dear Colleagues,
to make the installation of freeipa-client/ipa-client-install much
easier for SysAdmins, we should add a call to pam-auth-update, in
platform/debian.py.
This is one of the missing links, to make freeipa-client installation
going smoothly.
There needs to be
** Bug watch added: fedorahosted.org/freeipa/ #2455
https://fedorahosted.org/freeipa/ticket/2455
** Also affects: freeipa via
https://fedorahosted.org/freeipa/ticket/2455
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of FreeIPA
Public bug reported:
Dear Colleagues,
after successfully joining a freeipa domain with 12.04, it should be
possible to use ipa-getkeytab from the freeipa-client package.
Sadly this is just an expectation.
so, "ipa-getkeytab --help" on F17 gives this output:
[root@authmgr ~]# ipa-getkeytab --he
** Attachment added: "ipa-getgeytab.strace.1204.log"
https://bugs.launchpad.net/bugs/1025864/+attachment/3226389/+files/ipa-getgeytab.strace.1204.log
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net
** Attachment added: "ipa-getkeytab.strace.f17.log"
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1025864/+attachment/3226390/+files/ipa-getkeytab.strace.f17.log
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https
timo
i just compiled freeipa 2.2.0 and this looks more broken (running it
on f17 and there it works)
ipa client install breaks with a glibc trace
debian.py needs more adjustment ( patch will be send tomorrow)
so i think something i wrong with our deps i think
furthermore i did some backports for
timo
if i can of help with upstream
Jr aquino is just sitting Some cubicals next to me so i have a direct
wire to upstream ;-)
actually with him i am working on this project
so whatever it takes we have everything in place
Sent from my iPhone
On 18.07.2012, at 00:55, Timo Aaltonen wrote:
>
actually for us its critical to have at least a working package of the
client
but i do my best to have an overlay pkg in our own repos which works
until there is a better solution :-)
so be warned that more bug reports are coming in ;-)
have a nice holiday :-)
Sent from my iPhone
On 18.07.2012
Ok,
the bug occurs as well on ipa-join.
Anyways...found the bug.
if locales are not configured correctly it will fail, because the call to
ret=init_gettext() fails and all utils are exiting.
WIll close it
** Changed in: freeipa (Ubuntu)
Status: New => Invalid
--
You received this bug
Well,
I should be more precise...
I tried to use the pam config without libpam_cracklib (you know removing the
bits and pieces from the pam-auth-update config files, as described in the
other bugreport). But it didn't work out.
Couldn't login.
Adding libpam-cracklib to the list of installed pa
So,
what do we have, the service status calls are not parsed
correctly.
Even with dbus and sssd started, it still fires up the service dbus start and
service sssd start commands.
Actually, with FreeIPA 2.2.0 the whole debian platform module breaks.
So, it looks like we have to do much more on
What do you think we can have a fix for this from debian, or should we
go ahead and do it on ubuntu first?
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1024765
Title:
ipa-client-install fail
*** This bug is a security vulnerability ***
Public security bug reported:
Needs to be fixed in Ubuntu.
Sadly CVE Identifier is still not public.
Anyways, fixes are already public:
See RHEL Announcement.
Security Advisory - RHSA-2013:0189-1
Public bug reported:
Hi,
running on CentOS/RHEL 6 the stable FreeIPA Server version 3.0.0
Using an ipa client from 12.04 works as expected.
Now I am testing enrolling of Raring and Saucy in FreeIPA and this
fails.
Client Version is 2.47 (from 3.1.2 pkg) and server version is 2.46 (from
RHEL/Ce
@Timo: This fix in trusty is good, but doesn't help.
The ipa-client after 12.04 LTS are not compatible anymore with the working IPA
server from RHEL.
This client can't talk to an older IPA master serverso 12.04 LTS is still
stucked.
RH doesn't plan to update IPA Server to a new version.
--
Sure,
I'll still have an ipa server wiht 3.0 running on my local kvm infra...
I test trusty...but it's more the protocol which fails not the client
installation.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.lau
22 matches
Mail list logo
