lshell lets you restrict a user's shell environment to limited sets of
commands, choose to enable or disable any command over SSH (e.g. SCP,
SFTP, rsync, etc.) log user's commands, implement timing restrictions,
and more.
WWW: https://github.com/ghantoos/lshell/
===> The following configuration options are available for lshell-0.9.18.20160916:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove expired ports:
2020-09-15 audio/abraca: Uses deprecated version of python
2020-09-15 audio/ardour5: Uses deprecated version of python
2020-09-15 audio/cplay: Uses deprecated version of python
2020-09-15 audio/cpp-xmms2: Uses deprecated version of python
2020-09-15 audio/p5-xmms2: Uses deprecated version of python
2020-09-15 biology/haplohseq: Uses deprecated version of python
2020-09-15 biology/tophat: Uses deprecated version of python
2020-09-15 chinese/ibus-array: Uses deprecated version of python
2020-09-15 comms/congruity: Uses deprecated version of python
2020-09-15 comms/libbtbb: Uses deprecated version of python
2020-09-15 comms/quisk: Uses deprecated version of python
2020-09-15 databases/mtools-mongodb: Uses deprecated version of python
2020-09-15 databases/mydbf2mysql: Uses deprecated version of python
(Only the first 15 lines of the commit message are shown above )
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Regular USE_GITHUB cleanup.
Do not set DISTNAME.
Do not set WRKSRC, if you feel like you need to, you should fix
GH_PROJECT instead.
Sponsored by: Absolight
shells/lshell: update to 0.9.18.20160916
- pass maintainership to submitter
- switch to github
- add NO_ARCH, update project web-page and remove unneded patch
This release fixing some vulnerabilities, that defeats the purpose
of the package entirely, so this is why MFH is requested.
PR: 215989
Submitted by: Damien Fleuriot <dam@my.gd>
MFH: 2017Q1
shells/lshell: Fix immediate exit after first command
Without this fix, using lshell is impractical as the shell exits after
the first command is executed.
PR: 208003
Submitted by: Ignace Mouzannar
- Convert ports from korean/, shells/, x11/, x11-clocks/, x11-fm/,
x11-fonts/, x11-toolkits and x11-wm to new USES=python
Approved by: portmgr (implicit)
Reset the 99 ports still listed under sylvio@
Sylvio's last commit was 17 months ago, a full 5 months after all of his
ports could have been reset per policy. Given the push to complete
staging (48 ports are still unstaged, something like 70+ have already
been staged by other committers) and given that PRs are automatically
assigned but never addressed, it's better just to reset all the ports and
PRs so that it's clear to others that these ports are free to maintain.
Approved by: portmgr (implicit)
Add an @shell keyword to handle adding and remove a shell path in /etc/shell
Bump port revision of all ports that were doing it wrong prior to the keyword
CR: D208
Reviewed by: antoine
With hat: portmgr
lshell lets you restrict a user's shell environment to limited sets of commands,
choose to enable or disable any command over SSH (e.g. SCP, SFTP, rsync, etc.)
log user's commands, implement timing restrictions, and more.
WWW: http://lshell.ghantoos.org
PR: ports/137369
Submitted by: Sylvio Cesar <scjamorim@bsd.com.br>
Reviewed by: myself
