Verizon Fios Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Sunday, 10 November 2013

Too Much Information, by: David Haskell, Book Review

Posted on 18:29 by Unknown

When I saw this book was available to be reviewed I was very excited. It looked very intriguing and I was looking forward to trying out a new genre. The book is very well written, but as I was reading it I slowly became aware that the techno thriller genre doesn't really capture my interest. It has great mystery and suspense but the subject just couldn't hold my attention.
I've started a new position at work so it may just be the fact that I have to much on my mind right now. I will be giving this book another go in the future, maybe in a few months. If you love techno thriller books then you should give this one a try. If you don't then this is probably not the book for you.

I received one or more of the products mentioned above for free using Tomoson.com. Regardless, I only recommend products or services I use personally and believe will be good for my readers.
Read More
Posted in amazon, blogging, Blogging with The Tate's, books, david haskell, product reviews, products, techno thriller, too much information | No comments

Friday, 8 November 2013

VERIZON... What did you change?

Posted on 10:28 by Unknown
For two years now, Digital Operatives has hosted some systems on Verizon FIOS.   Largely it has been trouble free.  That is until about a week ago.

About a week ago,  two employees (eventually 3) described an issue that they were having connecting to the mail server and ssh server residing on this network.

When connected via their home FIOS connection, they would be able to establish a TCP connection,  and then the connection would timeout before any meaningful data could be communicated.

This happened to several of our employees,  but not all employees that had FIOS,  who connected from their home Verizon FIOS networks.

Those same employees,  could connect with the same system and establish strong connections, while connected via Comcast, or AT&T phone tether.

What makes this weirder,  is we have another chat server that those same employees could connect to and maintain connections despite the problems with SSH and mail.

What accounted for the difference?  Why would this happen?  

It took a few days for us to not just cough it up to something strange or intermittent.  Anybody that has ever dealt with an ISP's tech support, knows it is not going to be a terribly enjoyable experience.

Nevertheless,  after several days of troubleshooting (getting through the stages of Verizon help) they insisted on sending us a "new" Modem/Router.  This was tremendously frustrating as we are not "run of the mill" users,  and couldn't logically explain why it wasn't something inside Verizon's internal network as opposed to the router that we've had for two years.  

Before waiting for the router,  we decided to do some old school Internet troubleshooting.

Using the ping command with the -s option,  you can send packets with different sizes.

(From Server side)
ping <employee ip>      100% connectivity

ping -s 500 <employee ip>      100% connectivity

ping -s 1500 <employee ip>     0% connectivity    ???????   Strange

ping -s 1499 <employee ip>    100% connectivity

What in the hell?  Are you telling me that some router on Verizon's network can't handle 1500 byte packets?

Sure enough,  we changed the MTU size on the SSH server and mail server.   Connections were established and maintained just fine.  No more issues....

Somewhere inside Verizon's network is likely to be a misconfigured router or switch.   Not sure I know how to tell the right person.   Even if they are using a protocol or format that doesn't support 1500 byte MTU,  shouldn't they at least support fragmentation on those links?

The world may never know.   Good luck playing Call of Duty GHOSTS with your Verizon peers when the PS4 comes out.




Read More
Posted in | No comments

Thursday, 10 October 2013

Digital Operatives Professional Training Courses...

Posted on 12:56 by Unknown

Successful hackers must continuously learn and adapt to ever evolving and multi-faceted challenges presented by a changing technology landscape.  Hacking and computer security courses are traditionally offered at hacking conferences, and individuals fly early to conferences to take relevant courses.  This model is expensive for companies wanting to stay on the bleeding edge, desiring to train all professionals on staff.  In hard economic times, budgets are constrained, and it may be unrealistic for a company to send 12 people to a remote conference for training when you include airfare and hotels.

To help our fellow industry professionals and hackers alike, Digital Operatives has developed a suite of courses that can be taught at any location.  We are able to travel to your facilities as long as you can provide the basic requirements for the course.  Our courses are designed to be both fun and informative in order to keep the attention of students.  Our classes typically end on the final day with some form of a competition that covers materials learned.

Classes Offered:
  • Security 101: Through the eyes of hackers
  • Hacker Scripting: The Python Way
  • Advanced Cyber Trade-craft and Reverse Engineering
  • Fuzzer Development and Vulnerability Discovery
  • Advanced Vulnerability Research and Exploit Development
  • Computer Security for Lawyers: Protecting your clients information
  • Hands On Privacy Management
We can develop custom courses tailored directly to your company's needs.

If you're interested in learning more contact us at: contact@digitaloperatives.com
Read More
Posted in | No comments

Once upon a time there were Bell Labs...

Posted on 07:17 by Unknown
Today is another step closer to the end of an era for the old AT&T Bell Labs (now called AT&T Labs). Our estimated colleague David Korn (inventor of the famous Korn Shell - ksh) is leaving the labs, and he sent us the following farewell message in a form of (what else?) a Korn Shell script:


cd /tmp
if [[ $(print hello) != hello ]] 2> /dev/null
then echo 'You should use ksh'
alias print=echo
fi
trap 'rm mvs2*' EXIT
trap 'print "$year: dgk raptured to dgk@xxxxxxxxx"' TERM
for x in 76 78 80 81 83 86 87 88 89 90 91 93 95 99 100 103 107 108 110 112 113
do case $((year=1900+x)) in
1976) print "$year: Hello Bell Telephone Labs, Holmdel; Goodbye NYU";;
1978) print "$year: create 'formshell' for RBCS from Bourne shell";;
1980) print "$year: leave Bell Telephone Labs and return to NYU";;
1981) print "$year: return to Bell Telephone Labs Murray Hill Bldg 5"
print "$year: meet erg north dgb and kpv";;
1983) print "$year: first version of ksh with editing and job control";
print "$year: dgb becomes my supervisor"
print "$year: UNIX for apollo with erg and ed fisher";;
1986) print "$year: compete with kpv for best malloc library";;
1987) print "$year: win best one liner in obfuscated C contest"
print "$year: began long and continuing collaboration with gsf";;
1988) print "$year: KornShell 88 book published";;
1989) print "$year: 3d file system with gsf and ekrell";;
1990) print "$year: sfio with kpv";;
1991) print "$year: begin ast library with gsf";;
1993) print "$year: first version of ksh93";;
1995) print "$year: 1993 KornShell book published"
print "$year: first version of UWIN"
print "$year: Bell Labs split to AT&T Labs and Lucent";;
1997) print "$year: move to Florham Park";;
1999) print "$year: y2k testing software created";;
2000) print "$year: ast software becomes self documenting";;
2003) > mvs2pc; print "$year: create mvs2pc";;
2007) print "$year: Universal Biller invoicing runs with msv2pc";;
2008) print "$year: UWIN merged into VizGems written in ksh by Dr. ek"
print "$year: merged mfcobol compiler into mvs2pc";;
2010) print "$year: distributed shell using coshell";;
2012) mv mvs2pc mvs2cloud; print "$year: rename mvs2pc to mvs2cloud";;
2013) kill -TERM $$;;
esac
done
exit



Read More
Posted in ksh, UNIX | No comments

Sunday, 29 September 2013

Pretzel Crisps Review

Posted on 17:37 by Unknown

We love pretzels and we love chips and now we can have the best of both worlds with Pretzel Crisps. The taste and texture of a pretzel and the ability to dip or stack like chips and crackers. The flavors are amazing. Cody's personal favorite was the Garlic Parmesan and the Chipotle Cheddar. I enjoyed all of the hot ones, they are so full of flavor. They offer ten different flavors: Classic, Supreme, Tuscan Three Cheese, Cinnamon Toast, Original, Garlic Parmesan, Buffalo Wing, Everything, Sesame, JalapeƱo Jack, and Chipotle Cheddar. And for the holidays they have Dark Chocolate & Peppermint and White Chocolate & Peppermint. You can buy Pretzel Crisps at a local retailer or from Pretzel Crisps.


"Pretzel Crisps® are a modern twist on an old favorite.  They combine the best part of the pretzel – all the flavor and crunch – but lighter, crispier and more versatile than ever before.  Since 2004, Pretzel Crisps® have reinvented the pretzel category winning over the hearts and taste buds of snackers everywhere as the world’s first spreadable pretzel-shaped cracker.  With its thin, crunchy, high-quality ingredients and sweet and savory flavors, it’s no wonder Pretzel Crisps® are the go-to, better-for-you snack choice."
We would just like to say, we enjoyed every second of this review. This product has become a must buy in the Tate household and if you like pretzel we highly recommend this product. 

Disclaimer: We were sent these products for free from Pretzel Crisps® to review for our honest opinion. We only recommend products or services we use personally and believe will be good for our readers. Your opinions may vary from our opinions.

Read More
Posted in blogging, Blogging with The Tate's, Florida, full of flavor, happy husband, Husband and Wife perspective, man and women perspective, Pretzel Crisps, Pretzels, product reviews, products, snacks, yummy | No comments

Wednesday, 25 September 2013

CSAW CTF 2013 Qualification Round: Reversing

Posted on 09:30 by Unknown

Each year, the Information Systems and Security Laboratory (ISIS Lab) of the Polytechnic Institute of New York University hosts a Cyber Security Awareness Week, bringing together students and researchers to discuss the latest in cybersecurity.  Cybersecurity has always been the core focus at Digital Operatives and we are looking forward to this year's events in November.  The 2013 CSAW Capture the Flag Qualification Round was held this past weekend with over 1300 participating teams.  Like most Jeopardy-style CTFs, CSAW had several categories of problems, with Reverse Engineering as one of them.  A small team from Digital Operatives participated in this competition; below are write-ups for the Reversing problems.  Congratulations to the winning teams and great job to the organizers of the competition!

Contents

  • Reversing 100: DotNetReversing.exe
  • Reversing 100: csaw2013reversing1.exe
  • Reversing 150: bikinibonanza.exe
  • Reversing 200: csaw2013reversing2.exe
  • Reversing 300: crackme
  • Reversing 400: keygenme32.elf
  • Reversing 500: Noobs First Firmware Mod
  • Reversing 500: Impossible

Reversing 100: DotNetReversing.exe

We are prompted for a passcode and, upon attempting "a", the program crashes with a System.FormatException by attempting to parse the input as a number.

Upon opening the program in IDA Pro, it is quite clear where the branch between success and failure is, and because we know the program is looking for a numerical input, the constants just above this branch stand out.

We see that the program takes 0xC5EC4D790 and 0xF423ABDB7 and XORs them.

The result is 0x31cfe6a27, or 13371337255 in base ten, so we try this as input and get the flag!

Flag: I'll create a GUI interface using visual basic...see if I can track an IP address.



Reversing 100: csaw2013reversing1.exe

When the program is run, it displays a jumbled mess as the flag. Something clearly went wrong.

IDA Pro shows that the program only goes into its decryption routine if a debugger is attached.

We simply run the program with IDA as a debugger and allow it to display the decrypted flag.

Flag: this1isprettyeasy:)



Reversing 150: bikinibonanza.exe

This program gives various failure messages when we enter a string, including misleading messages about adding or subtracting 3 to our string input.

Because the program is in .NET IL, we open it with Red Gate's .NET Reflector and find the relevant procedures.  The code takes the string "NeEd_MoRe_Bawlz" and the current hour (plus one), feeds them into another procedure, and compares the result with our input.  If they match, the program will display the flag.

The procedure that operates on the hour and fixed string calls another procedure that substitutes the values, then finally calculates an MD5 sum over the string.

We convert this code into Python so that we can run it over all 24 hours and get the valid inputs.

#!/usr/bin/python

import md5

key_string = "NeEd_MoRe_Bawlz"

def substitute(num2, num1):
s = [ 2, 3, 5, 7, 11, 13, 0x11, 0x13, 0x17, 0x1d, 0x1f, 0x25, 0x29, 0x2b,
0x2f, 0x35, 0x3b, 0x3d, 0x43, 0x47, 0x49, 0x4f, 0x53, 0x59, 0x61, 0x65,
0x67, 0x6b, 0x6d, 0x71 ]
return s[num1] ^ num2

def get_key(text1, num1):
t = ''
for num2 in xrange(len(text1)):
ch = text1[num2]
for num in xrange(num1):
ch = chr(substitute(ord(ch), num+1))
num += 1
t += ch;
return md5.new(t).hexdigest()

for i in xrange(24):
print get_key(key_string, i)

reversing-150.py

Finally, we feed the correct input for the computer's hour into the program and get the flag.

Flag: 0920303251BABE89911ECEAD17FEBF30



Reversing 200: csaw2013reversing2.exe

We initially run the program and nothing happens, so we'll open it in IDA Pro.  We simply start the binary in IDA's local debugger and guide the program to branch to the correct code, then examine memory just before the program terminates.

Alternatively, we could increment esi before allowing the call to MessageBoxA for the flag.

Flag: number2isalittlebitharder:p



Reversing 300: crackme

IDA Pro reveals that the file is an ELF that prompts for a key, hashes it, and succeeds if the hash equals 0xef2e3558.

The hash algorithm is a modified Bernstein hash with 1337 used as the start value instead of 5381.

unsigned int hash(char* s) {
unsigned int h = 1337;
while(*s) {
h = 33*h + *(s++);
}
return h;
}

We code up the algorithm and run it through Digital Operatives' constraint solver to generate matching strings.


~}?Jyjx
t~6pKpl
gt7_En;
*,2>bds
2k{].?=
GJJ4GSv
Piqqtoa
...

We send it off to the server and get the flag!

Flag: day 145: they still do not realize this software sucks



Reversing 400: keygenme32.elf

This file is an ELF; running it with no arguments gives:

usage: ./keygenme32.elf <username> <token 1> <token 2>

Analysis in IDA Pro shows this program creates a virtual CPU, executes an instruction stream with our provided username, then compares the two tokens to two of the registers within the virtual CPU via a check() function.

Rather than reversing the entire CPU instruction set, we write a GDB script to pull the values from the virtual CPU's registers and then derive the correct tokens.

break *0x804a2a2
run
file ./keygenme32.elf
x/xw $ebp+8
x/xw $ebp+12
kill
quit

script.gdb

#!/usr/bin/python

import socket
import re
import subprocess

server = '128.238.66.219'
port = 14549

prompt_pattern = re.compile('give me the password for (.*)')
gdb_pattern = re.compile('0x........:\t(0x........)')
gdb_command = ['gdb', '--batch', '-x', './script.gdb', '--args',
'./keygenme32.elf', 'WILL_BE_REPLACED', '0', '0']

# connect
s = socket.socket()
s.connect((server,port))

while True:
# get the prompt
prompt = ''
while prompt.find('give me the password for') == -1 and \
prompt.find('key') == -1:
prompt += s.recv(65536)
if prompt.find('key') != -1:
print prompt
s.close()
exit(0)
prompt = prompt.split('\n')
prompt = filter(None, prompt)
print repr(prompt)
prompt = prompt[-1]
name = prompt_pattern.match(prompt).group(1)

# place the name in the command
gdb_command[6] = name

# run it
p = subprocess.Popen(gdb_command, stdout=subprocess.PIPE)
output = p.communicate()[0]
print 'got output: '+output

# get values
output = output.split('\n')
output = filter(None, output)
token1 = gdb_pattern.match(output[-3]).group(1)
token2 = gdb_pattern.match(output[-2]).group(1)

# transform
token1 = int(token1, 16)
token1 ^= 0x31333337

token2_1 = token2[2:4]
token2_2 = token2[4:6]
token2_3 = token2[6:8]
token2_4 = token2[8:]
token2 = int('0x' + token2_3 + token2_1 + token2_2 + token2_4, 16)

# send the reply
reply = '%d %d\n' % (token1, token2)
print 'sending: '+reply
s.send(reply)

reversing-400.py

We run the Python script and get the flag!

Flag: r3vers1ng_emul4t3d_cpuz_a1n7_h4rd!



Reversing 500: Noobs First Firmware Mod

We are given a modified U-Boot firmware.  After setting up QEMU within an Ubuntu server virtual machine, we can use IDA Pro's Remote GDB Debugger to step through the code and analyze.  One of the first things U-Boot does is relocate itself from 0x00010000 to 0x07fd7000.  We can compensate for this in IDA by rebasing the program:

RebaseProgram(0x07fc7000, MSF_FIXONCE);

After digging around, we find a new command has been created, csaw, corresponding to the internal do_csaw function shown below.

The function, as hinted, has a bug in it: it attempts to copy from an empty/invalid memory address, 0x80002013. There is one other reference to this address, in the smc_init function, which tries to copy the string "SUPERSEXYHOTANDSPICY" there.  (The full string in the binary is actually "key!=SUPERSEXYHOTANDSPICY".)

Thus, we replace the two invalid addresses in do_csaw with the appropriate ones.  The remainder of do_csaw is supposed to extract characters from this string to construct the key, but again there is a bug — one of the pointers for the memcpy in its extraction loop is not incremented.  We code up some debugger hooks in IDC to do the work for us.

#include <idc.idc>

static fix_r5_and_r11()
{
SetRegValue(0x7feac27, "R5");
SetRegValue(0x7feac4f, "R11");
return 0;
}

static increment_r10()
{
SetRegValue(GetRegValue("R10") + 1, "R10");
return 0;
}

static main()
{
AddBpt(0x7fd8df0);
AddBpt(0x7fd8e10);
AddBpt(0x7fd8e34);
SetBptCnd(0x7fd8df0, "fix_r5_and_r11()");
SetBptCnd(0x7fd8e10, "increment_r10()");
}

reversing-500.idc

Flag: SPREYOADPC



Reversing 500: Impossible

We get a file, impossible.nds.  Analyzing strings in it reveals it is a Nintendo DS game file.  We load it up in no$gba and notice there are lots of debug strings printed, including "RENDER SHIP" and "RENDER WTF".  By placing read-access breakpoints on those strings, we can get context of the game state while tracing through each frame render.  An analysis of the registers leads us to an area of memory containing game time, score, and enemy HP, shown below.

Killing the enemy by modifying its HP causes the game to render a screen with the key, at which point we search the emulator memory for "key" and find the whole string.

Flag: ou6UbzM8fgEjZQcRrcXKVN

Read More
Posted in | No comments

Monday, 23 September 2013

CSAW CTF 2013 Qualifiers: Crypto 300 Writeup

Posted on 09:55 by Unknown
The CSAW Capture The Flag online qualifiers were held last weekend (9/19/2013 through 9/22/2013). The top 10 undergraduate teams will participate in the CSAW CTF finals in November; however the qualifiers were open to everyone and a small team from Digital Operatives participated. Below is a writeup of one of the Crypto challenges:

The Crypto 300 challenge was contained entirely in a tarball that contains a custom encryption Python script and nine encrypted files. The encryption algorithm reuses a single 256-byte key to XOR each subsequent block of the input file. Simple XOR encryption of uncompressed files often leads to the key sticking out of the ciphertext when the input file contains many zeroes. This is also the case with some rudimentary binary packers that XOR data inside themselves. In the case of Crypto 300, thousands of blocks were given to us in the ciphertext files, providing many opportunities to find (0 XOR key[i]) instances scattered throughout the files. For instance, if at byte offsets 0+blocksize * x (where x is a non-negative integer) in the ciphertexts frequently contains 0x40, it is likely that byte 0 of the key is 0x40.


We created a simple Python script to count the number of times each byte value occurs at each block offset.

#!/usr/bin/python
import os
import sys

blocksize=256
prefix="output/file"
suffix=".enc"

blocks=[]

for x in range(0,9):
        fxname = prefix + str(x) + suffix
        try:
                print "Opening " + fxname
                fx = open(fxname,'rb')
        except:
                print "Failed to open " + fxname
                continue
        moretoread = True
        while moretoread:
                block = fx.read(blocksize)
                if(len(block) < blocksize):
                        moretoread = False
                        print "Last block was " + str(len(block)) + " bytes."
                blocks.append(block)        

print "Extracted " + str(len(blocks)) + " blocks."

#Calculate the number of times each byte value occurs at each position in a block
histogram = [[0 for i in range(blocksize)] for j in range(blocksize)]
for block in blocks:
        for b in range(0, len(block)):
                val = ord(block[b])
                histogram[b][val] = histogram[b][val] + 1

#Get the most used byte value for each position in the block
maxvals=[0 for i in range(blocksize)]
for hidx in range(0, len(histogram)):
        bytearr = histogram[hidx]
        cur_max_pos = 0
        cur_max_count = 0
        for idx in range(0,len(bytearr)):
                count = bytearr[idx]
                if count > cur_max_count:
                        cur_max_count = count
                        cur_max_pos = idx
        maxvals[hidx] = cur_max_pos

f = open("newsecretkey.dat","wb")
f.write(bytearray(maxvals))
f.close()

print "Done"

With the key in our newsecretkey.dat we are then able to decrypt all of the files from the challenge output folder using our new secret key and some simple Python borrowed from onlythisprogram.py.

#!/usr/bin/python
import os
import sys
import argparse

blocksize=256

parser = argparse.ArgumentParser(description="Decryption")
parser.add_argument('--infile', metavar='i', nargs='?', type=argparse.FileType('r'), help='input file, defaults to standard in', default=sys.stdin)
parser.add_argument('--outfile', metavar='o', nargs='?', type=argparse.FileType('wb'), help='output file, defaults to standard out', default=sys.stdout)
parser.add_argument('--secretkey', metavar='s', nargs='?', type=argparse.FileType('a+'), help='output file, defaults to secretkey.dat', default='secretkey.dat')

args = parser.parse_args()

counter=0
args.secretkey.seek(0)
keydata = args.secretkey.read(blocksize)
print "Using secret key: "
print keydata

while 1:
        byte = args.infile.read(1)
        if not byte:
                break
        args.outfile.write(chr(ord(keydata[counter % len(keydata)]) ^ ord(byte)))
        counter+=1

sys.stderr.write('\nSecret keyfile: %s\nInput file: %s\nOutput file: %s\nTotal bytes: %d \n' % (args.secretkey.name, args.infile.name, args.outfile.name, counter))

Use the following commands with the above decrypt.py:

./decrypt.py --infile=output/file4.enc --outfile=file4.enc.gz --secretkey=newsecretkey.dat
gzip -d file4.enc.gz
vim file4.enc
:set nowrap

After decryption we have nine plaintext files.  The fifth file (file4.enc) is a gzip compressed ASCII file that contains a message and the key: BuildYourOwnCryptoSoOthersHaveJobSecurity

For Hackers nostalgia, play the MIDI file0! 


Read More
Posted in | No comments
Older Posts Home
Subscribe to: Posts (Atom)

Popular Posts

  • How to compile busybox with Android NDK for both ARM and x86 architectures
    I was looking for a way to run busybox on a Motorola RAZRi with an x86 Intel Atom processor but I couldn't find any Android app from th...
  • Security and Trust when Everything has a Computer In It
    Security and Trust when Everything has a Computer In It Recently, Panic Software announced that they had opened up an HDMI display adapter ...
  • Sony Cyber-shot DSC-HX200V 18.2 MP 30 x High Zoom GPS Digital Camera - BLACK
    Sony Cyber-shot DSC-HX200V 18.2 MP 30 x High Zoom GPS Digital Camera - BLACK Blogger Opportunity Giveaway from June 17 to  July 12 Come and ...
  • Free Blogger Opp – Timjan Design Malachite 5/1
    Here comes another Visionary Bri blogger opportunity. Sign up now for the Timjan Bloomers Giveaway. Our sponsor, Timjan Design , has offered...
  • Hackers that solve problems...
    The nation and the world at large are struggling to come to grips with the fact that we are now more than ever vulnerable in our daily lives...
  • How to build Python-4-Android for the ARM Neon
    Currently the Py4A project does not compile for the ARM Neon architecture. If you try to run ndk-build on the project by setting the APP_A...
  • How to Cross-Compile libiconv for Android
    If your legacy C/C++ code includes <iconv.h> to convert the encoding of characters from one coded character set to another, and you ne...
  • How to compile libogg for Android
    To compile libogg for Android, you just need to create an appropriate jni/Android.mk makefile with the minimum set of files and options need...
  • Problems with new version of rpmbuild
    The Problem With the new version of rpmbuild installed on CentOS 6.x, if you try to use an old RPM spec file, you will get an error like the...
  • Sony Cyber-shot DSC-HX200V Giveaway
    Hosted by: NYSavingSpecials and Your Fashion Resource ,  Co-hosted by Melissa Say What? ,  Barbara's Beat ,  LibbysLibrary ,  Confessio...

Categories

  • amazon
  • amazon.com
  • Android
  • Apple
  • Arduino
  • ARM
  • baby
  • baby reviews
  • back to school
  • beef jerky
  • bicycle. wagon
  • bike
  • Blanket Buddies
  • blogging
  • Blogging with The Tate's
  • books
  • busybox
  • camera
  • camera giveaway
  • candle giveaway
  • candles
  • CaseApp
  • CentOS
  • coffee
  • david haskell
  • dermorganic
  • DHCP
  • digital camera
  • events
  • Florida
  • Fortran
  • free blogger giveaway
  • free blogger sign-ups
  • full of flavor
  • giveaways
  • GNU
  • GPON
  • hair care
  • happy husband
  • Hot tea
  • Husband and Wife perspective
  • iMac
  • ipad
  • iphone
  • iphone case
  • iphone case review
  • Javascript
  • Keurig Coffee Review
  • Keurig Review
  • Kindle
  • ksh
  • LifeProof iPhone Case Review
  • Linux
  • MacOSX
  • Malachite Bloomers
  • man and women perspective
  • meat
  • Mips
  • Network
  • Pretzel Crisps
  • Pretzels
  • product reviews
  • products
  • Python
  • Router
  • scentsy
  • scentsy candles
  • school
  • scooter
  • security system
  • skin care
  • snacks
  • sony
  • sony cyber-shot
  • Stuff Animal
  • suface pro
  • Summer
  • summer fun
  • surface pro giveaway
  • techno thriller
  • Timjan Design
  • too much information
  • UNIX
  • vegan
  • vegan products
  • verizon
  • verizon fios
  • VitaminsBaby
  • waterproof case
  • Windows
  • x86
  • yummy

Blog Archive

  • ▼  2013 (41)
    • ▼  November (2)
      • Too Much Information, by: David Haskell, Book Review
      • VERIZON... What did you change?
    • ►  October (2)
    • ►  September (3)
    • ►  August (3)
    • ►  July (2)
    • ►  June (2)
    • ►  May (6)
    • ►  April (8)
    • ►  March (2)
    • ►  February (5)
    • ►  January (6)
  • ►  2012 (17)
    • ►  December (3)
    • ►  November (4)
    • ►  October (8)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile