Devan Goodwin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If so could you take a look at an F10 blocker for 0.5:
https://bugzilla.redhat.com/show_bug.cgi?id=487618
While the crash is bad, I think it might only be happening when
authentication fails, there seems to be a credentials problem with
router-users.xml in newer jabberd versions as outlined in the ticket.
(filed a separate ticket against jabberd with respect to crashing if
authentication fails in general) I think we just need to sort out the
credentials and we can go ahead with F10 but I don't know enough about
jabberd or how we use it to know what options we have.
Thanks,
Devan
- --
Devan Goodwin <dgood...@redhat.com>
Software Engineer Spacewalk / RHN Satellite
Halifax, Canada 650.567.9039x79267
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkm3FgQACgkQAyHWaPV9my4b2wCgrQBB/zR7X+4/WFX9Yx7hupe8
z1MAniJeznAVl1qbvA5gK4CH3wvC1nXE
=x6DD
-----END PGP SIGNATURE-----
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Suspect setting 'secret' within router.xml and router-users.xml should
work for our needs.
I be honest in saying do not understand this setting, but this is what
we have historically used. I am sure that there is some jabber docs that
explains it, make sure that its not now some huge security hole.
Wish I had an Centos 5 and F10 box to login and compare the files to see
better what you have seen :)
Cliff
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
