2:02 a.m.
Jeremy Eder writes:
That's not a satisfactory answer, I guess, but every input helps, so
thanks a lot!
Okay so I guess if I ramble on about my Archlinux attempts then it won't
be dismissed out of hand. A user called "irtimmer" has submitted a storaged
source package to the Archlinuxs AUR repository and I ended up maintaining
the cockpit-git package. Archlinux currently uses systemd v209 by default.
https://aur.archlinux.org/packages/storaged
https://aur.archlinux.org/packages/cockpit-git
FWIW cockpitd and cockpit-ws seem to run but when I browse to https://localhost:21064/
I can't login, most likely because of this...
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
dlopen(/usr/lib/security/pam_sepermit.so): /usr/lib/security/pam_sepermit.so: cannot open
shared object file: No such file or directory
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM adding faulty module:
/usr/lib/security/pam_sepermit.so
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/password-auth
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/postlogin
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/password-auth
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/password-auth
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
dlopen(/usr/lib/security/pam_selinux.so): /usr/lib/security/pam_selinux.so: cannot open
shared object file: No such file or directory
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM adding faulty module:
/usr/lib/security/pam_selinux.so
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/password-auth
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM _pam_load_conf_file: unable to open
/etc/pam.d/postlogin
Feb 25 17:49:21 tosh cockpit-ws[6824]: Returning error-response 500 with reason `Module is
unknown'
There are no standard selinux packages for Archlinux but there are a range
of selinux source packages in the AUR repo.
This message is mainly to let you know that cockpit is almost working on
Archlinux and if someone could give me a list of the most likely selinux
packages used on a Redhat system that applies to cockpit then I'll build
them locally and see if I can get to the next level of logging in.
https://aur.archlinux.org/packages/?K=selinux
2:29 a.m.
Mark Constable <markc(a)renta.net> writes:
Okay so I guess if I ramble on about my Archlinux attempts then it
won't
be dismissed out of hand.
Definitely not! :-)
A user called "irtimmer" has submitted a storaged
source package to the Archlinuxs AUR repository and I ended up maintaining
the cockpit-git package. Archlinux currently uses systemd v209 by default.
https://aur.archlinux.org/packages/storaged
https://aur.archlinux.org/packages/cockpit-git
Oho, cool! But please don't advertise these two packages as 'stable' or
'useable' just yet...
FWIW cockpitd and cockpit-ws seem to run but when I browse to
https://localhost:21064/
I can't login, most likely because of this...
Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
dlopen(/usr/lib/security/pam_sepermit.so):
/usr/lib/security/pam_sepermit.so: cannot open shared object file: No
such file or directory
Cockpit has its own PAM module, and you need to adjust it for your
distribution. I think there is no good way around this, or is there?
There are no standard selinux packages for Archlinux but there are a
range of selinux source packages in the AUR repo.
Cockpit doesn't depend on SELinux, it's just that our current PAM config
file is very Fedora specific because we were lazy. Let's fix that now!
I'll try to strip it down so that it works out of the box with upstream
PAM (if there is such a thing).
2:47 a.m.
On 25.02.2014 09:29, Marius Vollmer wrote:
Mark Constable <markc(a)renta.net> writes:
> Okay so I guess if I ramble on about my Archlinux attempts then it won't
> be dismissed out of hand.
Definitely not! :-)
> A user called "irtimmer" has submitted a storaged
> source package to the Archlinuxs AUR repository and I ended up maintaining
> the cockpit-git package. Archlinux currently uses systemd v209 by default.
>
> https://aur.archlinux.org/packages/storaged
> https://aur.archlinux.org/packages/cockpit-git
Oho, cool! But please don't advertise these two packages as 'stable' or
'useable' just yet...
> FWIW cockpitd and cockpit-ws seem to run but when I browse to
https://localhost:21064/
> I can't login, most likely because of this...
>
> Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
> dlopen(/usr/lib/security/pam_sepermit.so):
> /usr/lib/security/pam_sepermit.so: cannot open shared object file: No
> such file or directory
Cockpit has its own PAM module, and you need to adjust it for your
distribution. I think there is no good way around this, or is there?
Marius is right, but in the interest of clarity, this is not a 'PAM
module' but a 'PAM config'. Carry on ...
Stef
6:01 a.m.
----- Original Message -----
From: "Stef Walter" <stefw(a)redhat.com>
To: cockpit-devel(a)lists.fedorahosted.org
Sent: Tuesday, February 25, 2014 3:47:40 AM
Subject: Re: More basic newbie questions
On 25.02.2014 09:29, Marius Vollmer wrote:
> Mark Constable <markc(a)renta.net> writes:
>
>> Okay so I guess if I ramble on about my Archlinux attempts then it won't
>> be dismissed out of hand.
>
> Definitely not! :-)
>
>> A user called "irtimmer" has submitted a storaged
>> source package to the Archlinuxs AUR repository and I ended up maintaining
>> the cockpit-git package. Archlinux currently uses systemd v209 by default.
>>
>> https://aur.archlinux.org/packages/storaged
>> https://aur.archlinux.org/packages/cockpit-git
>
> Oho, cool! But please don't advertise these two packages as 'stable'
or
> 'useable' just yet...
>
>> FWIW cockpitd and cockpit-ws seem to run but when I browse to
>> https://localhost:21064/
>> I can't login, most likely because of this...
>>
>> Feb 25 17:49:21 tosh cockpit-ws[6824]: PAM unable to
>> dlopen(/usr/lib/security/pam_sepermit.so):
>> /usr/lib/security/pam_sepermit.so: cannot open shared object file: No
>> such file or directory
>
> Cockpit has its own PAM module, and you need to adjust it for your
> distribution. I think there is no good way around this, or is there?
Marius is right, but in the interest of clarity, this is not a 'PAM
module' but a 'PAM config'. Carry on ...
Oh, something to do with pam ? I couldn't login to my laptop this morning...on the
gdm screen briefly flashed something about pam_nologin. Rebooted and was able to login.
Don't see anything interesting in syslog.
Bizarre/fun :-)
3:49 a.m.
Marius Vollmer <marius.vollmer(a)redhat.com> writes:
I'll try to strip it down so that it works out of the box with
upstream
PAM (if there is such a thing).
https://github.com/cockpit-project/cockpit/pull/222
4:03 a.m.
On 02/25/14 19:49, Marius Vollmer wrote:
Bingo. I just manually edited my /etc/pam.d/cockpit and I was able to login
to the interface. The System Information dashboard is simply beautiful :)
FWIW...
Feb 25 19:58:04 tosh cockpit-ws[7466]: New connection from ::1:44117 for root@localhost
Feb 25 19:58:04 tosh systemd[1]: Starting user-0.slice.
Feb 25 19:58:04 tosh systemd[1]: Created slice user-0.slice.
Feb 25 19:58:04 tosh systemd[1]: Starting Session c1 of user root.
Feb 25 19:58:04 tosh systemd[1]: Started Session c1 of user root.
Feb 25 19:58:04 tosh systemd-logind[193]: New session c1 of user root.
Feb 25 19:58:04 tosh systemd[1]: Starting User Manager for UID 0...
Feb 25 19:58:04 tosh kernel: type=1006 audit(1393322284.737:4): pid=7498 uid=0 old
auid=4294967295 new auid=0 old ses=4294967295 new ses=3 res=1
Feb 25 19:58:04 tosh systemd[7498]: pam_unix(systemd-user:session): session opened for
user root by (uid=0)
Feb 25 19:58:04 tosh systemd[7498]: Starting Paths.
Feb 25 19:58:04 tosh systemd[7498]: Reached target Paths.
Feb 25 19:58:04 tosh systemd[7498]: Starting Timers.
Feb 25 19:58:04 tosh systemd[7498]: Reached target Timers.
Feb 25 19:58:04 tosh systemd[7498]: Starting Sockets.
Feb 25 19:58:04 tosh systemd[7498]: Reached target Sockets.
Feb 25 19:58:04 tosh systemd[7498]: Starting Basic System.
Feb 25 19:58:04 tosh systemd[7498]: Reached target Basic System.
Feb 25 19:58:04 tosh systemd[7498]: Starting Default.
Feb 25 19:58:04 tosh systemd[7498]: Reached target Default.
Feb 25 19:58:04 tosh systemd[7498]: Startup finished in 84ms.
Feb 25 19:58:04 tosh systemd[1]: Started User Manager for UID 0.
Feb 25 19:58:04 tosh cockpit-session[7496]: pam_unix(cockpit:session): session opened for
user root by (uid=0)
Feb 25 19:58:05 tosh cockpit-ws[7466]: Error processing request: Error reading request
line: TLS connection closed unexpectedly (g-tls-error-quark, 6)
Feb 25 19:58:05 tosh cockpit-ws[7466]: Error processing request: Error reading request
line: TLS connection closed unexpectedly (g-tls-error-quark, 6)
Feb 25 19:58:05 tosh cockpit-ws[7466]: New connection from ::1:44118 for root@localhost
Feb 25 19:58:05 tosh systemd[1]: Starting Session c2 of user root.
Feb 25 19:58:05 tosh systemd-logind[193]: New session c2 of user root.
Feb 25 19:58:05 tosh systemd[1]: Started Session c2 of user root.
Feb 25 19:58:05 tosh cockpit-session[7505]: pam_unix(cockpit:session): session opened for
user root by (uid=0)
Feb 25 19:58:05 tosh cockpit-ws[7466]: Error processing request: Error reading request
line: TLS connection closed unexpectedly (g-tls-error-quark, 6)
Feb 25 19:58:06 tosh cockpit-ws[7466]: Error processing request: Error reading request
line: TLS connection closed unexpectedly (g-tls-error-quark, 6)
Feb 25 19:58:06 tosh cockpit-ws[7466]: Error processing request: Error reading request
line: TLS connection closed unexpectedly (g-tls-error-quark, 6)
6:23 a.m.
Mark Constable <markc(a)renta.net> writes:
On 02/25/14 19:49, Marius Vollmer wrote:
> https://github.com/cockpit-project/cockpit/pull/222
Bingo. I just manually edited my /etc/pam.d/cockpit and I was able to login
to the interface.
Great!
Feb 25 19:58:05 tosh cockpit-ws[7466]: Error processing request:
Error
reading request line: TLS connection closed unexpectedly
(g-tls-error-quark, 6)
Yes, I see these, too. We need to figure out what's going on there.
3:54 a.m.
On 02/25/14 18:29, Marius Vollmer wrote:
> https://aur.archlinux.org/packages/storaged
> https://aur.archlinux.org/packages/cockpit-git
Oho, cool! But please don't advertise these two packages as 'stable' or
'useable' just yet...
Sure. It's a given AUR source packages are "use at your own risk".
I'll try to strip it down so that it works out of the box with
upstream
PAM (if there is such a thing).
That would be wonderful for non-rpm users. I just read the link below and I
really would not like to have to go through this just to satisfy a dependency
for cockpit when I have no other use for selinux.
http://www.jamesthebard.net/site/archlinux-selinux-and-you-a-trip-down-th...
3713
days inactive
3713
days old
cockpit-devel@lists.fedorahosted.org
8 comments
4 participants
participants (4)
-
Jeremy Eder -
Marius Vollmer -
Mark Constable -
Stef Walter