Current status

• port moved here from sysutils/qjail4 on 2018-11-01
  REASON: Has expired: Only for FreeBSD 10.x, use sysutis/qjail instead
  

Remove # $FreeBSD$ from Makefiles.

sysutils/qjail: Updaet to 5.5

1.  Change default ftp site to ftp from ftp12.
2.  Remove config -w and -W [Set vnet.interface NIC]
3.  Add -f flag to unmount command when releasing memory disc.
4.  Change so this version of qjail only runs on 12.0 and newer
    because pf is vimage aware now.
5.  If local install [-f] jump around stable, current check logic.
6.  Change/add logic & code to implement bridge/epair method for vnet jails.
7.  Change qjail.8 about vimage no longer having to be compiled into kernel 12.0
8.  Change "config -v logic to setup vnet jail with pf, ipf, ipf firewall.
9.  Add start vnet code to qjail script to check for host/vnet jail
    firewall mis-match.
10. Add start vnet code to boottime script to check for host/vnet jail
    firewall mis-match.

Convert to UCL & cleanup pkg-message (categories s)

Remove compatibility code for FreeBSD < 11.2 from all ports.

Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by:	rene
Reviewed by:	bapt, jbeich
Differential Revision:	https://reviews.freebsd.org/D17724

Update to 5.4.

Aaron Sachau sent email about bug he found. The "qjail console jailname"
command that has a jail with a fib assigned to it was not working correctly.
This error was introduced by changes done to correct coding syntax problems
that the hs-shellcheck package found and corrected and then published in
qjail-5.2. Reverted back to how qjail-5.1 did it. Aaron Sachau tested the
patch. Fixed now.

PR:		221839
Submitted by:	maintainer (Joe Barbish)

Update to 5.3

qjail-5.3-change-log

1. Adam Weinberger sent email about bug he found. The
   qjail console -c "ls /user/local" jailname
   command was not working correctly. This error was introduced by
   changes done to correct coding syntax problems that the hs-shellcheck
   package found and published in qjail-5.2. Fixed now.

2. Adam Weinberger also sent email containing a patch that standardized
   error messages and corrected some spelling errors.
   After review the patch was applied.

3. Checked all the 'kill' messages for 'Error:' prefix and added the

- Update to 5.2

PR:		218272

Update to 5.1.

PR:		217177
Submitted by:	maintainer
Sponsored by:	Absolight

Remove the remaining IGNORE_FreeBSD_9 lines.

Sponsored by:	Absolight

Remove the CONFLICTS_INSTALL lines, they can't conflict, they can't be
installed at the same time.

Submitted by:	maintainer
Sponsored by:	Absolight

Cleanup whitespace at EOL.

Pointy hat:	mat
Sponsored by:	Absolight

Update sysutils/qjail to 5.0 to handle FreeBSD 11+.

Copy it to sysutils/qjail4 for FreeBSD 10 and sync CONFLICTS with the
FreeBSD 8/9 version.

PR:		212201, 212202
Submitted by:	maintainer
Sponsored by:	Absolight

- Update to 4.9
- While here, add NO_ARCH

PR:		211145
Submitted by:	qjail1@a1poweruser.com (maintainer)

sysutils/qjail: 4.7 -> 4.8

There are changes to the internals of the jail(8) command and changes to
parameter names in the periodic files that have occurred in FreeBSD
Release 10.2 that effects jail behavior in a very minor way.

This version of qjail has an built in auto convert function that
fixes those minor behavior problems with existing jails. This auto
convert function is not documented in the qjail manual. Its only
shown in the port install output.  Issue [ qjail update -u ] from
the host console.

This will cause the existing "flavors" default & ssh-default
directories to be renamed and new ones populated. Then in each
existing jail the periodic.conf and newsyslog.conf files will be

- Update to 4.7

Changes:

1. When running "qjail create -c" option for creating a jail with ssh and
   a user id / password of the jail name. On first start the user id
   gets created in the jail. This first start status was not being
   turned off. Added code to start logic to fix this.

2. Did not like the way console function was handling console commands
   being passed to the jail for execution. Changed the logic so it works
   like this. If -c option used alone or if -c & -u used together,
   them default jexec command format used. If no -c option then
   "jexec jailname login -f <root or -u value>" format used.
   This is real login causing the Welcome message to display.

3. Corrected the qjail manual console function to document usage of
   -c and -u flags.

PR:		209737
Submitted by:	qjail1@a1poweruser.com (maintainer)

- Fix trailing whitespace in pkg-descrs, categories [p-x]*

Approved by:	portmgr blanket

Update to 4.6

PR:		208980
Submitted by:	Joe Barbish <qjail1@a1poweruser.com>
Sponsored by:	Essen Linuxhotel Hackathon 2016

sysutils/qjail: update 4.4 -> 4.5

PR:		208918
Submitted by:	Joe Barbish <qjail1@a1poweruser.com> (maintainer)

Update to upstream version 4.4

PR:		208851
Submitted by:	qjail1@a1poweruser.com (maintainer)

Fixup some whitespace at the beginning of lines problems.

With hat:	portmgr
Sponsored by:	Absolight

sysutils/qjail: 4.2 -> 4.3

PR:		206935
Submitted by:	Joe Barbish <qjail1@a1poweruser.com> (maintainer)

sysutils/qjail: 4.1 -> 4.2

- Correct "qjail config -n" routine logic

PR:		204601
Submitted by:	qjail1@a1poweruser.com (maintainer)

- Update to 4.1

PR:		202934
Submitted by:	qjail1@a1poweruser.com(maintainer)

Upgrae to 4.0.

PR:		199684
Submitted by:	maintainer

Upgrade to 3.9.

PR:		199651
Submitted by:	maintainer

Upgrade to 3.8.

PR:		199198
Submitted by:	maintainer

[MAINTAINER] sysutils/qjail: Update version 3.6=>3.7

- Add LICENSE (BERNE-CONVENTION)
- Change Maintainer email address
- Use @sample framework

PR:		199090
Submitted by:	qjail@a1poweruser.com

- Reset MAINTAINER due to fatal bounce

Reported by:	portscout

Cleanup plist

Upgrade to 3.6.

1. Add allow.mount.tmpfs parameter to build-jail.conf routine.
   Check if kernel tmpfs.ko has been loaded
   to host and if not then issue "kldload tmpfs" command.

2. Add code to config logic for lower case t to enable
   allow.mount.tmpfs parameter and upper case T to disable
   allow.mount.tmpfs parameter.

3. Remove -l null as method to disable nullfs and replace with
   upper case L to to disable nullfs.

4. Add upper case S to disable lower case s option.

sysutils/qjail: 3.4 -> 3.5

Updated qjail.bootime script for addition of allow.sysvipc
and ruleset parameters that were added to qjail script in qjail-3.4.

PR:		191660
Submitted by:	qjail@a1poweruser.com (maintainer)

- Update from 3.3 to 3.4
- Remove NEED_ROOT
- Update pkg-descr

Changelog: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191213#c0

PR:		ports/191213
Submitted by:	qjail@a1poweruser.com

sysutils/qjail: upgrade 3.2 -> 3.3

1. Fix typo in qjail.8 manual.
Change "See jailip below" to "See -4 option"

2. Fix typo in qjail-howto.8 manual as per PR# 186269.
Change a comma , inside of ip address to a . period.
73.x.97,51,10.0.10.126 to 73.x.97.51,10.0.10.126

3. Change qjail.portsnap.conf,
remove index-6 index-7 index-8 statements
replace index-9 with index-10

4. Removed rcvar=`set_rcvar` statement from qjail.bootime script.
In Release 10.0 its no longer included in the rc.d scripts and

Add NO_STAGE all over the place in preparation for the staging support (cat:
sysutils)

Re-add mistakenly removed CONFLICTS_INSTALL line

Update to version 3.2

qjail-3.2 change log

1. Added IPv6 support to "create" and "config" commands.

2. Changed the way jail status is determined. Now use "jls -j jailname jid"
 command instead of carring internal jid field in jail definition record.
 This fixed jail status problem when users used the "halt or reboot"
 command on the host instead of the "shutdown now" command.

3. Changed qjail-bootime script to nolonger populate internal jid field
 in jail definition record.

4. Corrected coding of conflicts_install parameter in the port Makefile

Register install conflicts with version 1.x

Submitted by:	maintainer via private email

- Update to 3.1

PR:		ports/179769
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

Register install conflict with sysutils/qjail2

Update to version 3.0

PR:		ports/179184
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

- Update to 2.2
- Unrestrict - license issue has been resolved

PR:		ports/178186
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

- Mark RESTRICTED

See: http://lists.freebsd.org/pipermail/freebsd-jail/2013-March/002118.html

With hat:	portmgr

Update to 2.1;

1. Added logic to interrogate the content of flavors for correctness
before allowing them to be merged into the newjail being created.
Only paths targeting directories holding configuration files are
allowed now. The jail create process is terminated and the offending
paths are listed in error messages.

2. Changed the /root/.cshrc file in both flavors default and ssh-default
to now contain setenv PACKAGESITE to point to packages-current
so login users of any jail will have the most current package
version available.

4. In the qjail install logic added code to create these additional paths
in basejail, /usr/ports/packages, /usr/home and /home link.

Update to 2.0;

Standard maintenance.

1. Added -c option on "qjail create" command that enables ssh access to the
jail and creates user account using jailname for id/pw.

2. Added -C option on "qjail create" command that depends on -D option that
creates ssh access to jail and creates user account using jailname for
id/pw while automatically duplicating jails.

3. Created a customized flavor, ssh-default that enables ssh access to jails.
This flavor contains a login account with id/pw of qjail.

4. Removed -c option from "qjail install" because hosts customized /etc
caused problems with jail start up.

5. Updated man qjail.8 to reflect the changes.

PR:		ports/174890
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

Update to 1.9:

	Added code to qjail install function to check for
	-STABLE, -PRERELEAASE, and -CURRENT versions running
	on the host and if so issue message that binary source
	is not available for download and to use the
	[qjail install -c] flag to clone the host system to
	populate the basejail with.

	Used setenv UNAME_r "9-stable" command on host to set
	release value seen by qjail.

PR:		ports/174644
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

Update to 1.8

uname -r shows 4 formats.
9.0-BETA1, 9.0-RC1, 9.0-RELEASE, and 9.0-RELEASE-p1
Logic added by 1.7 was supposed to correctly remove the -p1 string,
which it did if present, but if not present the -RELEASE gets removed
in error which results in the incorrect ftp url path for fetching the
install source.

Rewrote logic to handle -p suffix differently so it gets stripped
off leaving 9.0-RELEASE which is handled normally.

PR:		ports/174037
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)
Feature safe:	yes

Update to 1.7

On 'qjail install' command run on -BETA or -RC host has no binary distribution
source available by design. Added logic to check for this condition and issue
error message informing user.

On 'qjail install' command run on a host that has had security binary patches
applied results in [uname -r] command returning [Release-9.0-p3]. There is no
binary distribution source available by design for patched systems. Added code
to strip the -p3 suffix resulting in the 9.0-Release distribution source being
downloaded and used to populate the basejail.

PR:		ports/173394
Submitted by:	Joe Barbish (maintainer)
Feature safe:	yes

Update to 1.6

-a option means create new jail from archive file of jail-aaa.
Search of /usr/jails/archive selected incorrect archive file.
If archive files named jail-aaa, jail-aaa-bbb, jail-aaa-bbb-ccc were present
jail-aaa-bbb-ccc was always selected incorrectly.
This same logic was also used for 'qjail restore jail-aaa', but that logic
had check for this condition that told user to use full archive name that
included the date stamp archive was created.  Fixed logic in both functions.

PR:		ports/171724
Submitted by:	maintainer (Joe Barbish <qjail@a1poweruser.com>)

- Update to 1.5

PR:	ports/170012
Submitted by:	Joe Barbish <qjail@a1poweruser.com> (maintainer)

- Update to 1.4

PR:             ports/169466
Submitted by:   Joe Barbish <qjail@a1poweruser.com> (maintainer)
Approved by:    culot (mentor)

Restore missing newline

Submitted by:   ak

Update to 1.3;

  Updated script so that the perluglyhack code is added to the end of
  qjail update -b logic

PR:             ports/166666
PR:             ports/166917
Submitted by:   Joe Barbish (maintainer)

- Update to 1.2
- while here loop on install of man pages

Changed qjail to work with new path and single base
file install format now used in 9.0.

PR:     ports/165603
Submitted by:   maintainer, qjail@a1poweruser.com

Author silently changed distfile to correct manpage typos, chase distinfo.

PR:             ports/160645
Submitted by:   Joe Barbish <fbsd8@a1poweruser.com> (maintainer)

- Update to 1.1

PR:             ports/160574
Submitted by:   Joe barbish <fbsd8@a1poweruser.com> (maintainer)

Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail
system that includes security and performance enhancements. Plus a new level
of "user friendliness" enhancements dealing with deploying just a few jails or
large jail environments consisting of 100's of jails.

Qjail requires no knowledge of the jail command usage. It uses "nullfs" for
read-only system binaries, sharing one copy of them with all the jails.

Uses "mdconfig" to create sparse image jails. Sparse image jails provide a
method to limit the total disk space a jail can consume, while only occupying
the physical disk space of the sum size of the files in the image jail.

Ability to assign ip address with their network device name,
so aliases are auto created on jail start and auto removed on jail stop.