bucketworks PA project

Earlier last week I ended up making a new pa system for Bucketworks. Now what most people will not realize is everything at Bucketworks is hacked to gather and this is no different. I was asked to make a low power radio system for notifying people within Bucketworks for people at the door and other uses, seeing we would need to file for an fcc licence i decided to go another route and the Bucketworks pa project was born.

during our wondering around at Bucketworks we (paul,eli,and I) have come across manly things one of them things was an old pa speaker and I got to thinking does it still work? I ended up wiring one up to an amp, we found in the basement along with a old audio mixer seen below after finding out we had a bad 1/4″ cable.

and low and behold it worked.
https://www.youtube.com/embed/Lehy4tTpVCg

The next step was to figure out where all the rest of the speakers were located and where to run the wires back to the server room where we were going to store the audio equipment. we ended up finding a total of 5 speakers wired them in and played some Pandora over the new pa system. I had to modify a cable to go from the “server” to the audio board.

I then set to making the Bucketworks pa bot. This bot is a windows client that logs in into an irc channel and organically just sent text to a text to speech function over the sound board. I expanded it to authenticate, noaa weather warnings, play music, tell the time and a few other functions.

After showing it to a few guys we ended up hearing this and we all started laughing.

and the Bucketworks pa project was complete.
If there is any interest i will upload the code if it is wanted.

Some awesome useful irssi scripts.

If you dont already know to use scripts you have to put any scripts in:

/home/< your_user >/.irssi/scripts/

And to load it into irssi use:

/script load < script_name.pl >

adv_windowlist.pl – If you have lots of windows open in irssi like me this script will make your life much easier. It adds a permanent advanced window list in a statusbar by default. You can configure it to put it on a sidebar if you like.

trackbar.pl – This little script will do just one thing: it will draw a line each time you switch away from a window. This way, you always know just up to where you’ve been reading that window 🙂 It also removes the previous drawn line, so you don’t see double lines.

nickcolor.pl – In channels with lots of activity, all nicks having the same old white color can get a little crazy, this script gives each user is own color and put a little organization to the chaos.

spell.pl – Spell check for irssi. This script takes a little setup. first you have to install Lingua::Ispell and Ispell using the following commands:

$ sudo apt-get install ispell liblingua-ispell-perl

It should pull in a number of other packages including a dictionary. I actually received an error as well, but it seems safe to ignore:

error in control file: `Index' value missing for format `info' at /usr/sbin/install-docs line 709, line 16.

Now load the script into irssi and bind Alt-s as a short cut to check the line you wish to send.
to bind Alt-s type the following into irssi:

/bind meta-s /_spellcheck

Also set the max guesses:

/set spell_max_guesses 3

Now your ready to use this script. After you type a message before you hit enter hit Alt-s and this script if you have any misspelled words and give you up to three guesses for correction.

Hyper-v User rights assignment

So if your like most admin’s you and have a bunch of Support staff some times its just easier to give them access to hyper-v then to have them wait for the admin to complete a simple task (ex.make a snapshot). The only issue with this is the fact they can do things we don’t want… for instance turn a machine off reboot change settings like nics along w/ creating new machines. So i went looking and apparently there is a way to restrict this so this post goes to show how we can.

Assigning Rights to hyper-v
Open mmc.exe

Click file then add/remote snap-in

Select authorization manager and hit add and ok

Then right click on Open Authorization Store….

Select XML file then hit browse

Goto \\Server_name\c$\ProgramData\Microsoft\Windows\Hyper-V\ and select InitialStore.xml

Then hit ok


Role Assignments
Select the Role we want to assign in this case its Administrator

Right click and click assign User and Groups then select from Windows and Active Directory…

Enter username you want to assign rights to. And hit ok

That user will now have admin rights.

Creating New Role Definitions
(what rights does this group have?)
Expand intialstore.xml -> Hyper-v services ->Definitions ->Role Definitions

Right click Role definitions and click new role Definitions

Then enter a name and click add…

Select Operations tab

Then add what rights you want that role to have by checking the checkbox and hitting ok, ok.

Now that we have a new role definitions created now we need to create role assignments see role assignments Section.

Role Assignments
Right click create new role assignment

Select what role that’s been defined

And hit ok

Now we need to add user into this group see Role Assignments

WDS Mananger on windows 8

Apparently Microsoft did not include WDS manager with there server 2012 RSAT (Remote Server Administration Tools) once again…
to enable remote wds control place the fallowing script in a batchfile and run batchfile.bat wdsservername

copy \\%1\c$\windows\system32\WdsMgmt.msc c:\windows\system32\WdsMgmt.msc
copy \\%1\c$\windows\system32\en-US\WdsMgmt.msc c:\windows\system32\en-US\WdsMgmt.msc
copy \\%1\c$\windows\system32\wdsmgmt.dll c:\windows\system32\wdsmgmt.dll
copy \\%1\c$\windows\system32\en-US\wdsmgmt.dll.mui c:\windows\system32\en-US\wdsmgmt.dll.mui
copy \\%1\c$\windows\system32\WdsImage.dll c:\windows\system32\WdsImage.dll
copy \\%1\c$\windows\system32\en-US\WdsImage.dll.mui c:\windows\system32\en-US\WdsImage.dll.mui
copy \\%1\c$\windows\system32\wdscsl.dll c:\windows\system32\wdscsl.dll
copy \\%1\c$\windows\system32\wdstptc.dll c:\windows\system32\wdstptc.dll
copy \\%1\c$\windows\system32\WdsTptMgmt.dll c:\windows\system32\WdsTptMgmt.dll
copy \\%1\c$\windows\system32\en-US\WdsTptMgmt.dll.mui c:\windows\system32\en-US\WdsTptMgmt.dll.mui
copy \\%1\c$\windows\system32\wdsmmc.dll c:\windows\system32\wdsmmc.dll
copy \\%1\c$\windows\system32\en-US\wdsmmc.dll.mui c:\windows\system32\en-US\wdsmmc.dll.mui
regsvr32 WdsMgmt.dll
regsvr32 WdsTptMgmt.dll
regsvr32 WdsMmc.dll

once you do its now possible to remotely manage wds servers in your network by typing WdsMgmt.msc in search.

dc414.org now hosting a tor exit node!!

dc414 is now hosting a tor exit node on our main server!! That’s two nodes running full time under the dc414 banner!

Here is the info on the tor server on dc414 – http://torstatus.blutmagie.de/router_detail.php?FP=0df6b76f92abbad09dfef4f2e3748c9ad75fe12c

Here is the info on the tor server I run from my house – http://torstatus.blutmagie.de/router_detail.php?FP=D6859BFF04AD1267DFC7B5646ED2A304B824FC21

I hope others follow our lead and set up exit nodes where ever they can! Got one running now? Comment to this post or send it in to us and we will drink a beer in your honor, for a job well done!

For the cause!

As some of you might know I run a Tor exit relay from my home connection. I got this in the mail the other day:

Hello and welcome to Tor!

We’ve noticed that your Tor node dc414 has been running long enough to be flagged as “stable”. First, we would like to thank you for your contribution to the Tor network! As Tor grows, we require ever more nodes to improve browsing speed and reliability for our users. Your node is helping to serve the millions of Tor clients out there.

As a node operator, you may be interested in the Tor Weather service, which sends important email notifications when a node is down or your version is out of date. We here at Tor consider this service to be vitally important and greatly useful to all node operators. If you’re interested in Tor Weather, please visit the following link to register:

https://weather.torproject.org/

You might also be interested in the tor-announce mailing list, which is a low volume list for announcements of new releases and critical security updates. To join, visit the following address:

https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce

Additionally, since you are running as an exit node, you might be interested in Tor’s Legal FAQ for Relay Operators (https://www.torproject.org/eff/tor-legal-faq.html.en) and Mike Perry’s blog post on running an exit node (https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment).

Thank you again for your contribution to the Tor network! We won’t send you any further emails unless you subscribe.

Disclaimer: If you have no idea why you’re receiving this email, we sincerely apologize! You shouldn’t hear from us again.

Yay my node is now stable!! Now we just need to get one running on the dc414 server 🙂