FreeBSD Bugzilla – Attachment 156948 Details for
Bug 200333
[NEW PORT] security/vm-to-tor: Framework to connect virtual machines to the tor network
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
vm-to-tor shar
vm-to-tor.shar (text/plain), 4.66 KB, created by
Yuri Victorovich
on 2015-05-19 15:54:32 UTC
(
hide
)
Description:
vm-to-tor shar
Filename:
MIME Type:
Creator:
Yuri Victorovich
Created:
2015-05-19 15:54:32 UTC
Size:
4.66 KB
patch
obsolete
># This is a shell archive. Save it in a file, remove anything before ># this line, and then unpack it by entering "sh file". Note, it may ># create directories; files and directories will be owned by you and ># have default permissions. ># ># This archive contains: ># ># security/vm-to-tor ># security/vm-to-tor/pkg-descr ># security/vm-to-tor/distinfo ># security/vm-to-tor/Makefile ># security/vm-to-tor/files ># security/vm-to-tor/files/pkg-message.in ># >echo c - security/vm-to-tor >mkdir -p security/vm-to-tor > /dev/null 2>&1 >echo x - security/vm-to-tor/pkg-descr >sed 's/^X//' >security/vm-to-tor/pkg-descr << '5054eaef859e68e4e918507c401602dc' >XFramework to connect any number of virtual machines to the >Xtor anonymity network. >X >XWWW: https://github.com/yurivict/vm-to-tor >5054eaef859e68e4e918507c401602dc >echo x - security/vm-to-tor/distinfo >sed 's/^X//' >security/vm-to-tor/distinfo << 'e7054b6434a5b064e4924e26ed375d10' >XSHA256 (yurivict-vm-to-tor-0.150519-17bdb91_GH0.tar.gz) = cc7255f0bfac1e29a4a00fd30e7903495fc46b7e4390ead999416cf6df375c8b >XSIZE (yurivict-vm-to-tor-0.150519-17bdb91_GH0.tar.gz) = 12564 >e7054b6434a5b064e4924e26ed375d10 >echo x - security/vm-to-tor/Makefile >sed 's/^X//' >security/vm-to-tor/Makefile << 'f9681e568c6f9a4e2bbef33bfdd7eece' >X# Created by: Yuri Victorovich <yuri@rawbw.com> >X# $FreeBSD$ >X >XPORTNAME= vm-to-tor >XPORTVERSION= 0.150519 >XCATEGORIES= security net >XMASTER_SITES= GH >X >XMAINTAINER= yuri@rawbw.com >XCOMMENT= Connect virtual machines to the tor network >X >XLICENSE= BSD4CLAUSE >X >XRUN_DEPENDS+= tor:${PORTSDIR}/security/tor \ >X tiny-dhcp-server:${PORTSDIR}/net/tiny-network-utilities >X >XUSE_GITHUB= yes >XGH_ACCOUNT= yurivict >XGH_PROJECT= ${PORTNAME} >XGH_TAGNAME= 17bdb91 >X >XNO_BUILD= yes >XNO_ARCH= yes >XSUB_FILES= pkg-message >X >XPLIST_FILES+= etc/rc.d/${PORTNAME} bin/vm-ctrl >XPLIST_FILES+= "@sample etc/${PORTNAME}.rc.conf.simple.sample" >XPLIST_FILES+= "@sample etc/${PORTNAME}.rc.conf.complex.sample" >X >X.include <bsd.port.pre.mk> >X >X.if ${OPSYS} == FreeBSD && ${OSVERSION} < 1000000 >XBROKEN= Does not work on FreeBSD versions earlier than 10 >X.endif >X >Xdo-install: >X ${INSTALL_SCRIPT} ${WRKSRC}/${PORTNAME} ${STAGEDIR}${PREFIX}/etc/rc.d >X ${INSTALL_SCRIPT} ${WRKSRC}/vm-ctrl ${STAGEDIR}${PREFIX}/bin >X ${INSTALL_SCRIPT} ${WRKSRC}/rc.conf.simple.sample ${STAGEDIR}${PREFIX}/etc/${PORTNAME}.rc.conf.simple.sample >X ${INSTALL_SCRIPT} ${WRKSRC}/rc.conf.complex.sample ${STAGEDIR}${PREFIX}/etc/${PORTNAME}.rc.conf.complex.sample >X @${REINPLACE_CMD} -e 's|"/usr/local"|"${LOCALBASE}"|' ${STAGEDIR}${PREFIX}/etc/rc.d/${PORTNAME} >X @${REINPLACE_CMD} -e 's|/usr/local|${LOCALBASE}|' ${STAGEDIR}${PREFIX}/etc/${PORTNAME}.rc.conf.*.sample >X @${REINPLACE_CMD} -e 's|etc/rc\.conf\.|etc/${PORTNAME}.rc.conf.|' ${STAGEDIR}${PREFIX}/etc/${PORTNAME}.rc.conf.*.sample >X >X.include <bsd.port.post.mk> >f9681e568c6f9a4e2bbef33bfdd7eece >echo c - security/vm-to-tor/files >mkdir -p security/vm-to-tor/files > /dev/null 2>&1 >echo x - security/vm-to-tor/files/pkg-message.in >sed 's/^X//' >security/vm-to-tor/files/pkg-message.in << 'a7602e1c3c99d6afd114a83931b0677a' >X====================================================================== >XYou installed vm-to-tor: framework that allows to connect virtual >Xmachines to the tor network. >X >XIt requires sysctl variable net.link.tap.user_open=1 set in >X/etc/sysctl.conf. >X >XTo start vm-to-tor manually, you can use this command: >X# service vm-to-tor onestart >XThis will connect an adapter tap0 to tor. Then you need to change >Xsettings of one virtual machine to use tap0 interface (in VirtualBox >Xyou need to set "Bridged Adapter" as a network type and choose tap0 >Xas an adapter name, in bhyve tap0 will just work). >X >XTo enable at system startup, you can add one of these lines: >X. %%PREFIX%%/etc/vm-to-tor.rc.conf.simple >Xor >X. %%PREFIX%%/etc/vm-to-tor.rc.conf.complex >Xto /etc/rc.conf, and modify %%PREFIX%%/etc/vm-to-tor.rc.conf.* >Xaccording to your needs. Please read there the explanation of >Xvm-to-tor features. >X >XBefore changing configuration, you need to stop vm-to-tor with >X# service vm-to-tor {one}stop >XAfter changing configuration, you need to start it again: >X# service vm-to-tor start >X >XTo see the status of vm-to-tor: >X# service vm-to-tor status >X >XTo connect to the virtual machine tap1 with ssh: >X# ssh 172.16.1.2 >X >XTo change tor router setting for machine tapN with ctrl protocol: >X# vm-ctrl tapN >X >XBy design, you can't connect to the host from the virtual machine for >Xsecurity reasons. Machine is isolated from the host environment, and >Xis not host-aware. Besides the optional NFS connection, all >Xcommunication initiated by the virtual machine happens only through >Xtor. >X====================================================================== >a7602e1c3c99d6afd114a83931b0677a >exit >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 200333
: 156948 |
156949
|
156950
|
156951