Landis Vinchattle An aggregation.

January 28, 2012

NTPD and the Terrible, Horrible, No Good, Very Bad Listening Sockets

Filed under: Security,Software — Tags: — Landis V @ 11:41 am
Trying to get ntpd to stop creating listening sockets is a royal pain in the ass. Sure, I can set a firewall rule that blocks access to the port on undesired interfaces, but it's more work to make that happen, and it's just not as clean. Here's what I finally ended up doing to stop creating default (0.0.0.0:123 for IPv4 and :::123 for IPv6) listeners and just set a listening socket on one address on my internal interface. Hopefully it helps someone else out.
 # Add to ntp.conf, in order
 interface ignore all
 interface ignore ipv4
 interface ignore ipv6
 interface listen 192.168.0.1

While there’s not a gaping security window with NTP, I just feel a little safer not having anything listening at all.

March 11, 2011

Much going on

Filed under: Communications,Family & Personal,Security,Software,Technology — Tags: — Landis V @ 12:44 am

My world is eventful at present, and it seems to be preventing me from properly accomplishing much of anything.  Last Saturday my wife and I got new cell phones, finally extricating ourselves from Verizon (don’t get me started…). US Cellular has done well for us thus far – my wife has already had a support issue, and it was handled to resolution in a courteous manner.  My experience with Verizon was always courteous, but never resolved.  As part of this, I finally have an Android phone – very exciting, and I am enjoying it a great deal.  I have loaded the Froyo pre-release ROM, and it’s doing fairly well.  Haven’t had enough time to really play in detail (phone is the Samsung Mesmerize… another good reason to get away from Verizon; no locked down, eFuse Moto’s here :)).  Was hoping to port my old Verizon number to my Google Voice account since they are now allowing porting of mobile numbers, but it appears that BFE Nebraska is not on their list of locations which they can support porting from.  So, I will have to see if US Cell can port it to my new phone post hoc.  Wish me luck :/.

Have also been trying to get the WordPress app for Android to work with my blog, but that doesn’t seem to be happening just yet.  Had some issues with the client on my BlackBerry as well, so I think the finger currently points at the hosting provider configuration and not the phone(s).  Will work on that when (if?) I get the time.  Will also get back to my experimentation and testing of LxC’s hopefully sooner than later.  However, with my wife in Chicago from Saturday through Monday and myself on parent duty, it will probably be later rather than sooner.

Did experiment a little bit with the live disc for Clonezilla recently.  Acquired a bunch of systems, some of which will be finding new homes as soon as I can get them finished.  For the handful that came with drives, I had built a Windows image on one of them and tested replicating it to others.   Since the systems were all of similar-to-near-identical configuration, imaging was surprisingly fantastic and generally fast.  Imaging to a test VirtualBox on my daily driver Ubuntu box didn’t work quite as well, but I suspect there were a number of factors impacting that including 32-vs-64-bit processor config.  Again, something to worry about later since the actual PCs did great.  Kudos to Clonezilla on that one.

Have been looking at some of the descendants of FreeS/WAN recently, specifically StrongSwan (don’t bite me on the case tonight, I’m friggin’ tired!).  Looks neat, and I was hopeful to get a chance to run a test drive with it.  Don’t think that will actually happen unless I can somehow get it done tomorrow night (yeah, right).  May perhaps do so at home if I get the time.  It has pushed me to a somewhat better understanding of IPSec (I think), especially Main Mode vs Quick Mode.  I will continue to look at it and hope to at least make it work in a lab environment in case I ever have need of it in the future.  My current direction, as a result of tight time constraints, is probably going to be the ASR series of Cisco routers if their licensing proves tolerable, and something in the 7206 G2/VSA category if not.  I’m hearing 1.8Gbps throughput on those boys at the low end (though I assume that’s with 1400 byte packets, it’s still quite something).

Anyway, have to call it for tonight and work on some POs.  Just really needed to get some of what was going on out of my head and down on “paper”.  There is something at least mildly therapeutic about writing 🙂

January 15, 2010

Hauppauge WinTV-HVR-1600 – Configuration under Mythbuntu

Filed under: Software,Technology — Tags: — Landis V @ 12:12 am

I wanted to get more put together on this, but in the interest of something that may be useful to others immediately I’d like to get it posted ASAP.  This (mostly) details my experience getting the HVR-1600 working under Mythbuntu 9.10.  There are a few things remaining to get functioning the way I’d like (primarily the TV/Music/etc. keys at the top of the remote, but for the most part it is working.  Specifically, I’d like to build out some scripts and patch files to make it easier for those with a bit less shell experience than myself, but we shall see if I get around to that or not.  If it helps you, please let me know.  Also, please be aware that I have proceeded with the kernel upgrade to 2.6.3-.17.

The links highlighted below were of huge help to me, so sincere kudos to those folks.

In step #2, found lines to be commented in <working directory>/v4l-dvb/v4l/Makefile.media, starting at line 825, commented out all lines for “firedtv*”, about 5 lines.  Tried to run setup.sh in the lirc sources, needed to ‘apt-get install dialog’ on mythbuntu.  Did that, ran setup.sh, saw absolutely nothing that apperaed relevant to my IR (a couple of different Hauppauge models, but nothing that I had been able to get working before with lirc… granted, I never had a device in /dev for my IR hardware before).  Skipped it for now since I already have a current version of lirc installed.
Built & installed OK, but got a “BUG: unable to handle kernel paging request at 72727563” when trying to modprobe.  Ran across an article at http://www.mail-archive.com/linux-media@vger.kernel.org/msg13962.html describing a fix for that particular bug.
Saved the patch off to the myth box in <working directory> as ir_null_fix.patch.  Located the file to be patched in the v4l-dvb directory I had extracted previously.  cd’ed to <working directory>/v4l-dvb/linux/drivers/media/IR and ran ‘patch -i <working directory>/ir_null_fix.patch’.  Command completed successfully.
Changed back to <working directory>/v4l-dvb and started midway through Step 2 from http://www.uluga.ubuntuforums.org/showpost.php?p=8257616&postcount=27, with a minor exception.  Once in the dir, issued a ‘make clean’, then resumed with ‘make’ and ‘make install’.
Once ‘make install’ completed, tried to modprobe ir-kbd-i2c, but experienced the same behavior I had exerienced previously (that is to say, BUG message thrown when viewing dmesg output and unable to rmmod ir-kbd-i2c).  Rebooted to clear out modules and start fresh, and after the reboot retried the modprobe.  No errors, and dmesg shows “Creating IR device irrcv0!
Edited /etc/lirc/lircd.conf and added an “include /usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge”.  Remarked the existing line for the “devinput” remote configuration.  Ran ‘irw’ and noted that the codes were showing for the HVR-1100.  Unfortunately, upon starting mythfrontend the remote no longer worked.
Went through myth control center, set back to Linux devinput.  Corrected the device and load modules in hardware.conf, added the more_remotes hauppauge under lircd.conf.  Then ran mythbuntu-lirc-generator.
« Newer Posts

Powered by WordPress