head	1.6;
access;
symbols
	RELEASE_8_3_0:1.4
	RELEASE_9_0_0:1.4
	RELEASE_7_4_0:1.4
	RELEASE_8_2_0:1.4
	RELEASE_6_EOL:1.4
	RELEASE_8_1_0:1.4
	RELEASE_7_3_0:1.4
	RELEASE_8_0_0:1.4
	RELEASE_7_2_0:1.4
	RELEASE_7_1_0:1.4
	RELEASE_6_4_0:1.4
	RELEASE_5_EOL:1.4
	RELEASE_7_0_0:1.4
	RELEASE_6_3_0:1.4
	PRE_XORG_7:1.4
	RELEASE_4_EOL:1.3
	RELEASE_6_2_0:1.3
	RELEASE_6_1_0:1.3
	RELEASE_5_5_0:1.3
	RELEASE_6_0_0:1.2;
locks; strict;
comment	@# @;


1.6
date	2013.02.18.21.46.33;	author svnexp;	state Exp;
branches;
next	1.5;

1.5
date	2012.11.17.06.01.19;	author svnexp;	state Exp;
branches;
next	1.4;

1.4
date	2007.01.31.14.09.54;	author pav;	state Exp;
branches;
next	1.3;

1.3
date	2005.11.14.17.07.07;	author sem;	state Exp;
branches;
next	1.2;

1.2
date	2005.06.15.20.23.33;	author ahze;	state Exp;
branches;
next	1.1;

1.1
date	2005.06.15.06.57.10;	author ahze;	state Exp;
branches;
next	;


desc
@@


1.6
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/312526
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@# New ports collection makefile for:    sasp
# Date created:        2 September 2004
# Whom:                sviat
#
# $FreeBSD: head/security/sasp/Makefile 312526 2013-02-18 21:13:02Z dinoex $
#

PORTNAME=	sasp
PORTVERSION=	0.1
PORTREVISION=	2
CATEGORIES=	security
MASTER_SITES=	${MASTER_SITE_LOCAL} \
		http://people.freebsd.org/~ahze/distfiles/
MASTER_SITE_SUBDIR=	ahze

MAINTAINER=	sviat@@OpenGEEKS.it
COMMENT=	A tool that permits to use a gateway whatever IP we have

LIB_DEPENDS=	net:${PORTSDIR}/net/libnet

NO_WRKSUBDIR=	yes
MAKE_ENV=	LIBNET_CONFIG="${LIBNET_CONFIG}"
PLIST_FILES=	sbin/sasp

LIBNET_CONFIG?=	${LOCALBASE}/bin/libnet11-config

.include <bsd.port.mk>
@


1.5
log
@Switch exporter over
@
text
@d5 1
a5 1
# $FreeBSD: head/security/sasp/Makefile 300897 2012-07-14 14:29:18Z beat $
d10 1
a10 1
PORTREVISION=	1
d19 1
a19 1
BUILD_DEPENDS=	${LIBNET_CONFIG}:${PORTSDIR}/net/libnet
@


1.4
log
@- Patch net/libnet* to versioned libraries and header files, so they can
  coexist

PR:		ports/103861
Submitted by:	alepulver
Tested by:	pointyhat
With hat:	portmgr
@
text
@d5 1
a5 1
# $FreeBSD$
@


1.3
log
@libnet update:
- move 1.0 obsoleted version to net/libnet10
  net/libnet is latest Stable Version
  net/libnet is latest Beta Version

- Fix all depended ports with a new DEPENDS scheme

- While I'm here fix security/yersinia build on 4.x
  (getopt_long and ncurses issues)

PR:		ports/85519 (based on)
Submitted by:	Stas Yakovlev <stas.yakovlev_at_gmail.com>
@
text
@d19 1
a19 1
BUILD_DEPENDS=	libnet*>=1.1.2,1:${PORTSDIR}/net/libnet
d22 1
d25 2
@


1.2
log
@- Reroll tarball and mirror on MASTER_SITE_LOCAL, the orignal tarball
  was tared up and gzipped twice and gnutar does not like that.

Pointed out by:	krismail
@
text
@d10 1
d19 1
a19 1
BUILD_DEPENDS=	 ${LOCALBASE}/include/libnet/libnet-types.h:${PORTSDIR}/net/libnet-devel
@


1.1
log
@- Add sasp
This is a tool that uses ARP poisoning  to  have  a  scenario
like this: we have a LAN and we want offer connectivity to every-
one coming here with his laptop for example. It could happen that
our  customer  has  his  network parameters already configured to
work correctly in his own LAN, but not working here. We can  have
then this scenario:
Customer's  host (10.0.0.2/8 and default gateway set to 10.0.0.1)
Our LAN (192.168.0.0/24 with real gateway 192.168.0.254).
All that we want is that our customer plugs his laptop  and  joins
the  internet without changing nothing of his network parameters.
Here comes this tool installed in my real gw(192.168.0.254)  It's
a  sort  of sniffer, because it sniffs broadcast ARP requests for
the gateway and answers that the gateway is itself In our example
our  customer's  laptop  sends  this request: arp who-has 10.0.0.1
tell 10.0.0.2 Now our gateway does the following: 1)  Sends  back
this  reply to 10.0.0.2: arp reply 10.0.0.1 is-at his_mac_address
2)Create the alias 10.0.0.254 (ARP is not routable so we need one
alias  for each subnet that is not our one) 3)Sends itself an ARP
reply to refresh his ARP cache
It is different from proxy arp for two reasons: first it runs  in
user  space,  then in this case we can plug machines belonging to
whatever subnet, while proxy arp is used in the case of only  two
different ones.

PR:		ports/79676
Submitted by:	Luigi Pizzirani <sviat@@opengeeks.it>
@
text
@d11 3
a13 1
MASTER_SITES=	http://sviat.opengeeks.it/codes/sasp/
@

