Verizon Fios Tech Support

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

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

Sunday, 25 August 2013

Krave Beef Jerky Review

Posted on 11:14 by Unknown


First off I have to say i was very excited to review this product, Krave Beef Jerky is right up my ally. I love meat, what can I say. I've tried not eating meat, it lasted about a week then I broke down and ate some delicious bacon. So when the wife (Aimee) came to me and said eat this meat and write a review for it I said "thank you." 
Krave jerky is awesome. They have a great variety of cool flavors that use all natural ingredients. I use to think that all jerky was dry and leathery strips of meat and that's how it was supposed to be. Man was I wrong, Krave Jerky is so moist and beautiful and tender. Oh how I wish there were more words in the dictionary, that I could think of at this moment, to explain the taste of this Jerky. It almost melts in your mouth, and you don't feel like you just ate something that was sitting in a vat of salt. Or something that was attached to a shoe at some point in time like some of the gas station Jerky I have had. The only time I have had something like this was when I have had home made jerky. But even then I have never had any with these flavors (Black Cherry Barbecue, Basil Citrus, Chili Lime, Garlic Chili Pepper, Lemon Garlic, Pineapple Orange, Grilled Sweet Teriyaki, and Sweet Chipotle) you can order them from KRAVE.
If you like jerky you will love this jerky, heck if you don't like jerky (like Aimee) you will more than likely love this jerky (like Aimee) it's just that good. 

Review by Cody Tate

Disclaimer: I was sent these products for free from KRAVE to review for my honest opinion. I only recommend products or services I use personally and believe will be good for my readers. Your opinions may vary from my opinions.


Read More
Posted in back to school, beef jerky, blogging, Blogging with The Tate's, Florida, happy husband, Husband and Wife perspective, man and women perspective, meat, product reviews, products, school, snacks, Summer | No comments

Friday, 23 August 2013

Defending Your E-Mails from Surveillance … Conveniently

Posted on 13:59 by Unknown
With the recent and ongoing disclosures of what appear to be widespread Internet surveillance programs, the public is becoming increasingly aware of the privacy risks in sending plaintext E-mail.  Even connecting to one's E-mail service provider using a cryptographically secure protocol like HTTPS provides a false sense of security, because one cannot ensure the trust or privacy of any intermediary servers/connections used to route the message to its recipient.  As such, there are many excellent tutorials—and even entire web campaigns—that empower average users to protect their online communications via free tools like OpenPGP.

Since day one, Digital Operatives has employed strong cryptography to protect all of its internal E-mail communications.  This works extremely well, and, for all intents and purposes, is currently very secure.  There are some downsides, however.  The number one complaint about using public key cryptography to secure all E-mail communications is that there really isn't a good way to search through the bodies of the E-mails in your inbox (since the message bodies are encrypted, a simple search for a term like "cat" or "meeting" won't match any of the E-mails it otherwise should have).  In fact, the second bug ever reported for the popular EnigMail GPG plugin for the Thunderbird mail client was a feature request asking for the ability to search through encrypted E-mail bodies.  That bug was opened in 2003 … and it is still open today.

The trouble is that the decryption step is too computationally expensive to decrypt all of the message bodies on the fly during the search.  The alternative would be to temporarily decrypt the message bodies of new E-mails as they arrive and add them to a search index.  The trouble is that this invites a security vulnerability, since sensitive message data would therefore be included in the search index.

Given that over 90% of the E-mail in our inboxes at Digital Operatives is encrypted, we decided to scratch our own itch and develop a solution to this problem.  We took the second approach mentioned above: We incrementally build a search index to search across the encrypted message bodies.  To mitigate the aforementioned security risk with this approach, we encrypt the entire search index using the same private key used to decrypt one's E-mails.  Therefore, the only risk would be if an adversary got access to one's private key, but that of course would have even worse security implications since he or she could then read all of the original E-mails anyway.

Our proof-of-concept solution is a tool called Magiic.  Magiic Allows for GPG Indexing of IMAP on the Command-line.  It is a Python script that uses GnuPG for encryption/decryption and Whoosh for full-text indexing.  It acts as a standalone mail application, connecting directly to an IMAP server and creating a local index off of the contents.  It has a simple ncurses interface so all interaction can take place on the command line.  We are releasing the code using a version of the Creative Commons BY-NC-SA 3.0 license that has been modified slightly to be more applicable for software licensing.  It is free for non-commercial use.  The code is available here.
Read More
Posted in | No comments

Thursday, 22 August 2013

How to debug Android Native Code with Eclipse

Posted on 06:29 by Unknown
This blog summarizes the steps needed to set-up your Eclipse environment to support the debugging of an Android native application written in C/C++. It's taken from Carlos Suoto's web page at http://www.eclipse.org/sequoyah/documentation/native_debug.php.

1. Pre-Requisites


  • Make sure you compile your C/C++ with the "-g" option (or use -DCMAKE_BUILD_TYPE:STRING="Debug" if you use cmake).
  • Make sure APP_OPTIM is set to "APP_OPTIM:=debug" in Android.mk and Application.mk.
  • Make sure build/core/build-binary.mk in Android NDK doesn't strip executables. For example patch android-ndk-r8e/build/core/build-binary.mk to the following:

    --- build/core/build-binary.mk.orig     2013-08-21 11:06:39.818329442 -0400
    +++ build/core/build-binary.mk  2013-08-21 11:13:11.877214361 -0400
    @@ -485,10 +485,16 @@ $(LOCAL_INSTALLED): PRIVATE_DST       :=
     $(LOCAL_INSTALLED): PRIVATE_STRIP     := $(TARGET_STRIP)
     $(LOCAL_INSTALLED): PRIVATE_STRIP_CMD := $(call cmd-strip, $(PRIVATE_DST))
     
    +ifeq ($(APP_OPTIM),debug)
    +$(LOCAL_INSTALLED): $(LOCAL_BUILT_MODULE) clean-installed-binaries
    +       @$(HOST_ECHO) "Install        : $(PRIVATE_NAME) => $(call pretty-dir,$(PRIVATE_DST))"
    +       $(hide) $(call host-install,$(PRIVATE_SRC),$(PRIVATE_DST))
    +else
     $(LOCAL_INSTALLED): $(LOCAL_BUILT_MODULE) clean-installed-binaries
            @$(HOST_ECHO) "Install        : $(PRIVATE_NAME) => $(call pretty-dir,$(PRIVATE_DST))"
            $(hide) $(call host-install,$(PRIVATE_SRC),$(PRIVATE_DST))
            $(hide) $(PRIVATE_STRIP_CMD)
    +endif

1.1. Install the Eclipse Sequoyah plugin


  1. In Eclipse go to Help -> Install New Software
  2. Click on the Add button
  3. Enter 'Sequoyah Metadata Repository' in the Name field
  4. Enter 'http://download.eclipse.org/sequoyah/updates/2.0/' in the Location field
  5. If you still see the "There are no categorized items" message, uncheck the "Group items by category" radio button
  6. Select "Sequoyah Android Native Code Support" and install the plugin

1.2. Convert The Android Java Application into C/C++ Project


You must convert your Java project to C/C++ using the Sequoyah plugin or else you won't be able to see the configuration options to set the proper debugger settings.
  1. In Eclipse select the Android Java project you need to convert
  2. Right click with the mouse and select Android Tools -> Add Native Support

1.3. Other Pre-Requisites


  1. The platform must be Android 2.2 (android-8) or later
  2. The ndk version must be r4b (it contains bugfixes to ndk-gdb that are necessary) or later
  3. Eclipse CDT 7.0 or newer must be installed
  4. The AndroidManifest.xml must have the property of the application node android:debuggable="true"
  5. The build must have been done with the ndk-build (if using the Sequoyah Android components, it will be automatic)

2. Configurations


  • 01) Create a debug configuration for an Android application (can be done with Eclipse or MOTODEV Studio)
  • 02) Create a debug configuration for a C/C++ application
  • 03) Set the following properties:

    http://www.eclipse.org/sequoyah/images/native_debug_2.png
  • 04) The process launcher must be the Standard Process Launcher. This is selected at the bottom of the Main tab:

    http://www.eclipse.org/sequoyah/images/native_debug_3.png
  • 05) On the "Main" tab:
    the Field C/C++ Application: $PROJECT_PATH/obj/local/armeabi/app_process
  • 06) On the "Debugger" tab:
    • field Debugger: gdbserver
    • On the "Main" subtab:

      http://www.eclipse.org/sequoyah/images/native_debug_4.png
    • 07) GDB debugger: $NDK_PATH/build/prebuilt/$ARCH/arm-eabi-$GCC_VERSION/bin/arm-eabi-gdb
    • 08) GDB command file: $PROJECT_PATH/obj/local/armeabi/gdb2.setup
      [Windows users] Uncheck the "Use full file path to set breakpoints" option
    • On the "Connection" subtab:

      http://www.eclipse.org/sequoyah/images/native_debug_5.png
    • 09) Type: TCP
    • 10) Hostname or IP address: localhost
    • 11) Port number: 5039 

    3. Instructions

  • Open the ndk-gdb script that came with the android NDK and comment the last line (we are not calling the usual gdb client, but we will attach an Eclipse gdb session instead):

    •     # $GDBCLIENT -x $GDBSETUP -e $APP_PROCESS
  • Insert a breakpoint in your Java code, preferably after all System.loadLibrary() calls. (To make sure that the debugger is correctly attached to the Java process)
  • Launch the android debug and wait for it to reach the breakpoint
  • From a Terminal session, in the project folder, run the modified ndk-gdb command. It should not attach to an gdb client, but call the gdbserver on the emulator and open a TCP port for connection (or in alternative if you have an Android device connected to your USB port, the ndk-gdb script will run gdbserver on the device itself).
  • In the $PROJECT_PATH/obj/local/armeabi/, modify the gdb.setup file, removing the target remote:5039 statement. (For some reason, the Eclipse GDB session does not like this statement being done in the commands file). Rename this new file to gdb2.setup. This step need to be run just once, on the first debug session.
  • Launch the C/C++ Application debug and wait for the Eclipse GDB session to fully connect to the emulator's gdbserver instance.
After following these steps, one can continue to debug the application as usual, using the "continue" option to let the execution flow until the next breakpoint is hit or by using the usual "step-in" to execute each statement individually. Setting a breakpoint on a Java statement that calls a native function through JNI and stepping into will place the user at the beginning of the native code.
Another way to set breakpoints in the C/C++ code is from Eclipse to click on File -> Open File and browse to the location of your source code. Then double-click on the line where you want to set the breakpoint.
Read More
Posted in Android, ARM | No comments

Tuesday, 9 July 2013

DermOrganics Review

Posted on 21:00 by Unknown
"DermOrganic® products are made using ingredients that are synergistic to your hair and skin to replenish from the outside what your hair and skin need inside for health and vitality. From the shampoo cleansers made from EFA lipids and amino acids, to conditioners blended with vegetable proteins, to treatments rich in natural moisture factors and all based on a proprietary lipid-rich emulsification systems, DermOrganic products outperform standard hair and skin care formulations to deliver exceptional results to salon treated hair." - from the DermOrganic website



I was pleasantly surprised with these products. First we'll talk about the hair products. Of late, I've been having issues with my hair.  I have to sleep with a CPAP machine and the straps make my hair flat and causes breakage. I started wearing a cap and that has solved the breakage issue, but its still flat.  After just one use of their hair products (shampoo, masque, and leave-in treatment), my hair already looked thicker. It left my hair feeling silky smooth after I washed it and its not so flat on top So I differently recommend these products. Another small notes, the smell of the hair product have a great scent to them.

Now about the facial products. Occasionally I get breakouts so I was excited to see how these products work. They have a soapless facial cleanser, facial moisturizer, and a hand & body moisture lotion. I was very happy with the results. My acne started clearing up almost immediately and it didn't leave my face dried out. And the lotion left my skin feeling soft and smooth. I definitely recommend these products. You can find their products at DermOrganic

Review by Aimee Tate

Disclaimer: I was sent these products for free from DermOrganic to review for my honest opinion. I only recommend products or services I use personally and believe will be good for my readers. Your opinions may vary from my opinions.
Read More
Posted in blogging, Blogging with The Tate's, dermorganic, hair care, product reviews, products, skin care, vegan, vegan products | No comments

Sunday, 7 July 2013

CaseApp Review

Posted on 11:50 by Unknown

Ok I have to say that I love personalizing stuff with things I like, I mean who doesn't. So if you like that and you don't have a tendency of dropping your phone, then you need to check it out HERE.  If lack of protection is an issue for you on your phone then this may not be the case for you. That's why this case is great for me but not for Aimee, she drops her phone a lot.This case will keep the back of your phone from minor scratches but not sure how safe it would be to drop it and I'm not going to test it. As you can see from the pictures this case is more for the look and you can pretty much customize it with any picture, including ones uploaded from your owe computer.Their website is very easy to navigate and picking a picture is easy. I got the case pretty quickly after picking the image, took less than a week.

So let's get to this...



Style : Love it, it doesn't add anything to the phone bulk or weight and you can personalize it as you can see I picked my favorite wrestler CM Punk.

Protection : Very little so if you are a person that drops your phone a lot this is not for you but if you are like me and are very aware of your phone safety you should be good but just be careful, this case is very thin and has no protection for the front of the phone.

Price : $34.00 I guess this is for the personalization process, it's a bit much for my taste.

Overall : I love it, but I am very careful with my phone. The personalization is what attracted me to it, the price makes me second guess it, but if you want something personalized its a good deal. 


Review written by Cody Tate.

Disclaimer: I was sent these products for free from CaseApp to review for my honest opinion. I only recommend products or services I use personally and believe will be good for my readers. Your opinions may vary from my opinions.

Read More
Posted in blogging, Blogging with The Tate's, CaseApp, Husband and Wife perspective, iphone, iphone case, iphone case review, man and women perspective, product reviews, products | No comments

Sunday, 16 June 2013

Sony Cyber-shot DSC-HX200V Giveaway

Posted on 20:49 by Unknown

Hosted by:
NYSavingSpecials and Your Fashion Resource, 

Co-hosted by
Melissa Say What?, Barbara's Beat, LibbysLibrary, Confessions Of A Mommy Of 5, Stay a Stay at Home Mom, Capri's Coupons,  Books R Us,  Mama Making Changes, Maria's Space, Monster Freebies, Simply Sherryl, Spaceships and Laser Beams, Quick Tattletails, Monica's Rants Raves Reviews, The Stuff of Succes and  Mom Knows It All


Come and join us on these great giveaway.  This is a great item for the summer.

One lucky winner will take a

Sony Cyber-shot DSC-HX200V
Value$479



US Only

June 17 to July 12

Enter below

Good Luck

a Rafflecopter giveaway

Disclosure:  Blogging With The Tate's is not responsible for prize.  If you have any questions about this giveaway please send an email to nysavingspecials@gmail.com.  All entries are optional, if you do any of the tasks you can collect the entries, even if you do one entry it will be counted on the giveaways as you did all of the tasks on that group, but if the winner tasks is a tasks you did not complete, a second winner will be chosen.  If the winner tasks is the one you did you will be the winner.
Read More
Posted in blogging, Blogging with The Tate's, camera, camera giveaway, digital camera, events, free blogger giveaway, giveaways, product reviews, products, sony, sony cyber-shot, Summer, summer fun | No comments
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

Popular Posts

  • Transferring Files from a computer to your Android device
    Android devices have file systems similar to regular computers. Subject to permissions restrictions, we can transfer files from a computer t...
  • Meeting The Tate's
       Hello, we are Cody and Aimee Tate. We live in Florida and have been married for 3 years. Recently we have decided to start doing product ...
  • Python For Android (Py4A)
    A better solution for cross-compiling Python for Android is to use the Py4A project which is made to be used together with SL4A (Scripting L...
  • 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...
  • Installing the Android SDK
    These instructions refer to a Ubuntu 12.04.1 LTS system running on an Intel processor. Head to the developer.android.com web site and downl...
  • Process Attribution In Network Traffic
    Author: Phil -at- DigitalOperatives Overview Digital Operatives recently completed a DARPA Cyber Fast Track (CFT) contract called  Process A...
  • Installing the Android NDK
    These instructions refer to a Ubuntu 12.04.1 LTS system running on an Intel processor. Head to the  http://developer.android.com/tools/sdk/n...
  • How to build the gcc Fortran cross-compiler for Android (ARM and x86)
    If you need to cross-compile for Android a program written in Fortran, you know already that the official Android NDK does not come with the...
  • LifeProof iPhone Case Review
       Today we are reviewing the LifeProof iPhone case, for iPhone 4 and 4S.  Like their slogan says its life-proof, which means waterproof, ...
  • 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...

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