Re: vlock command

Dmitry V. Levin
2012-11-14T23:54:28Z

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

On Wed, Nov 14, 2012 at 01:22:07PM +0100, Karel Zak wrote:
> On Wed, Nov 14, 2012 at 03:04:56PM +0400, Alexey Gladkov wrote:
> > http://git.altlinux.org/people/ldv/packages/vlock.git
>
> it seems the same code as the original vlock-1.3

It was surely based on the same vlock-1.3 code, and it has essentially the
same features list, but it's hardly the same code. :)

> > Some time ago, I have merged this version in kbd project:
> >
> > http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=tree;f=src/vlock;h=92419b98175d215a71f83bfb06b409daa97b13c4;hb=768b8c314e1d3c465d895b206da4aa4543914d1d
> >
> > I have a collection of utilities for manipulation in console (openvt,
> > chvt, deallocvt ...) I consider logical to have the utility for
> > terminal blocking.
> >
> > What do you think?
>
> Well, vlock is mostly about authentication,

About authentication? Well, could you then explain why do you keep that
7 year old vlock-1.3-morepam.patch from Nalin in Fedora vlock package?
It does something unnatural for vlock, e.g. pam_acct_mgmt and even
pam_setcred! At the same time, the only module in its account stack is
pam_permit.so. Weird.

--
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]