Google

Google SSL Certificates going to 2048-bit

Coming Soon! In August 2013, Google will start the process of switching its SSL Certificates over to 2048-bit for its services adding stronger security. This information was made public on Stephen McHenry’s, Director of Information Security at Google Blog.

The completion of this project is set to be completed by the end of the 2013 year.

Quoted on the blog Stephen McHenry writes

Most client software won’t have any problems with either of these changes, but we know that some configurations will require some extra steps to avoid complications. This is more often true of client software embedded in devices such as certain types of phones, printers, set-top boxes, gaming consoles, and cameras.

Stephen McHenry also listed a number of examples of improper validation practices that could lead to the inability of client software to connect to Google using SSL after the upgrade, such as matching any other certificate exactly or hard-coding the expected root certificate.

Change is coming soon! Don’t be left behind.

More detailed information can be found here

Google Crisis Response

Many of my friends may not know about this. I hope now they will and be better informed now and in the future. I feel the more you know, the more you can extend a helping hand to others. Google seems to have done just that by making critical information more accessible in times of disaster.

Google Crisis Response provides critical information and develops tools to support disaster relief. Some examples are:

  • Google Public Alerts disseminates relevant emergency alerts to users when and where they’re searching for them
  • Google Person Finder allows people to locate loved ones who have been impacted by a crisis
  • Google Crisis Maps was created to show damage and resources following emergency events.

Stop by http://www.google.org/crisisresponse and get informed and help if you can.

For more Google related projects head over to http://www.google.org/

How to remove Google+ hangout apps

Log into your Google account and find your way to your Google+

Next click on settings (gear icon), which take you into the accounts area

Click on security, then click edit on Authorizing applications and sites

Locate the Google+ hangout app you would like to remove (revoke access)
Click Revoke Access

The application should now be removed.

I wish this was a bit simpler, but it works for me; I hope this helps you out.

Shortcut to Authorizing applications and sites
https://accounts.google.com/IssuedAuthSubTokens?hl=en

Google Tasks, Ad Free

Google I/O is over and now a QR Code revealing a link and the ability to generate a code to unlock the Task Free Application for your phone. They are keeping it active for a few days, so be quick and spread the word about this.

Adding Google Voice to FreePBX

I followed the following steps to setup my new FreePBX Server with Google Voice.
I am happy to say it works for the most part, however inbound calls are not making it.  All in all this was a good learning experience:

*UPDATE*  I have made a follow up with my working configuration files

 

How To Add Google Voice To FreePBX

Part 1: In the shell

  1. Refer to the Asterisk Wiki: Calling Using Google. We’ll be following that as our guide.
  2. From the command line, as user root or asterisk, verify that the res_jabber and chan_gtalk modules are loaded.
    • [root@asterisk18 ~]# asterisk -rx "module show" | grep res_jabber
      res_jabber.so                  AJI - Asterisk Jabber Interface          0
      [root@asterisk18 ~]# asterisk -rx "module show" | grep chan_gtalk
      chan_gtalk.so                  Gtalk Channel Driver                     0
    • If one or both of those grep commands returns nothing, you need to build the modules (don’t forget to have OpenSSL development libraries installed) and make sure they are loading at Asterisk startup (autoload=yesOR load => res_jabber.so and load=> chan_gtalk.so in /etc/asterisk/modules.conf).
  3. There are three config files in /etc/asterisk to edit by hand (use vinanoemacs or whatever you like): jabber.conf, gtalk.conf, and extensions_custom.conf.
    • jabber.conf – Edit or replace jabber.conf to follow what is listed in Calling Using Google, and which I am pasting almost verbatim here. (I removed debug=yes.) This establishes the XMPP connection.[general]
      autoprune=no
      autoregister=yes
      [asterisk]
      type=client
      serverhost=talk.google.com
      username=your_google_username@gmail.com/asterisk
      secret=your_google_password
      port=5222
      priority=1
      usetls=yes
      usesasl=yes
      statusmessage=”I am an Asterisk Server”
      timeout=100
    • gtalk.conf – Again referring to the Asterisk wiki, edit gtalk.conf thus:[general]
      context=from-google
      allowguest=yes
      bindaddr=0.0.0.0
      ;externip=1.2.3.4 ; if you know your external ip addr
      stunaddr=stun01.sipphone.com ; use STUN if you're on dynamic IP and NAT
      [guest]
      disallow=all
      allow=ulaw
      context=from-google
      connection=asteriskSome notes about gtalk.conf:

      • Use context from-google, which we will set up in the extensions_custom.conf.
      • connection=asterisk must match the connection definition (in square brackets) in jabber.conf.
      • Use externip or stunaddr to get your external IP address if you’re behind a NAT.
    • extensions_custom.conf – Make a section like this:[from-google]
      exten => s,1,Answer()
      exten => s,n,Wait(2)
      exten => s,n,SendDTMF(1)
      exten => s,n,Set(CALLERID(num)=${CUT(CALLERID(name),@,1)})
      exten => s,n,Set(CALLERID(name)=${CUT(CALLERID(name),/,1)})
      exten => s,n,Goto(from-trunk,YOUR-GV-NUMBER,1)
      exten => s,h,Hangup

      • Replace YOUR-GV-NUMBER with your Google Voice DID.
      • The Set commands fix up the caller ID to get rid of the long XMPP ID that is passed on an inbound call.
  4. Once these files are in place, restart Asterisk (amportal restart).
  5. Issue the following command to see that the XMPP connection to Google Talk has been established:# asterisk -rx "jabber show connections"
    Jabber Users and their status:
    User: ...@gmail.com/asterisk     - Connected
    ----
    Number of users: 1
  6. Now you’re ready to set up a Google Voice trunk and inbound and outbound routes in FreePBX.

Part 2: FreePBX

  1. Add a new Custom Trunk.
    • Trunk name: Google Voice
    • Outbound Caller ID: put your Google Voice DID, even though this will be ignored (GV always uses your GV number for the outbound Caller ID)
    • Dialed Number Manipulation Rules: Google Voice requires that the number be a full 11 digits, starting with 1. Either here or in your outbound route (or both), make sure you are sending a full 11-digit number.
    • Custom Dial String: This is the most important part. Entergtalk/asterisk/+$OUTNUM$@voice.google.com where asterisk matches the client definition in your jabber.conf (in square brackets). If you’ve followed this how-to exactly, then this line is correct.
    • Submit changes.
  2. Add a new Outbound Route.
    • You can send any US domestic calls through Google Voice. Just configure an appropriate outbound route and select Google Voice as the trunk. I configured 11-, 10-, and 7-digit dialing within my own area code.
  3. Add a new Inbound Route.
    • Refer back to this line you entered in extensions_custom.conf: exten => s,n,Goto(from-trunk,YOUR-GV-NUMBER,1) Whatever you entered for YOUR-GV-NUMBER will be the DID you use for your inbound route.
    • Description: Google Voice (or whatever you want)
    • DID Number: YOUR-GV-NUMBER
    • Other stuff: defaults
    • Destination: wherever you want the incoming call to go.
  4. Submit all changes and apply configuration. Done! You have added a Google Voice two-way trunk to FreePBX and can use it in your inbound and outbound routing. Don’t forget to log in to Google Voice and select Google Chat (…@gmail.com) as the phone to which your incoming calls are forwarded!

 

A big thanks and all credit to the guys over at PSU VoIP

Android Market Reboot

Whoa, did you see that…

Well it wasn’t necessarily the black cat in the Matrix movie but something noticeable.

 

Visit https://play.google.com/store

How-To: install VMware .bundle on Ubuntu

By now many I have come accustom to installing programs using the apt-get method in Ubuntu, but there comes a time where we need to remember those other commands to install things.  For example when attempting to install software packaged in .bundle file format.

It all started when I downloaded VMware player and went to install the .bundle.  I wasn’t sure at that time what to do with it.  A Google search later I had my answer; and I hope Google got you to this page where I also share with you how-to do this.

In Ubuntu you open your command line terminal and type the following:

sudo sh VMware- ‘press tab to auto complete’

That’s it…   Follow the instructions and you are finished.

Vyatta Network Stats (NTOP) Install

I don’t have much to say here, other than I wanted to see something real time or close to it about how the traffic is flowing on my Vyatta Router so I looked for some info and found it.  I am sharing it here for others and future reference on my own part.

The first thing you must know is that to install NTOP you will need full root access.  The default vyatta user account will not permit you to do this install.  Please refer to a previous post of mine on how to enable root access in vyatta.

In addition to the above you will need to also give your vyatta router a public DNS server to use so it can download the necessary packages.  This is done by entering the configuration and typing ~# set system name-server 8.8.8.8 as you can see I used Google’s public name server.

And now on to the installation steps:

vyatta@vyatta:~$ configure
[edit]

vyatta@vyatta# set system package repository lenny components main
vyatta@vyatta# set system package repository lenny url http://http.us.debian.org/debian
vyatta@vyatta# set system package repository lenny distribution lenny
vyatta@vyatta# commit
vyatta@vyatta# save
vyatta@vyatta# su –

vyatta:~# aptitude update

vyatta:~# aptitude install ntop tcpd

vyatta:~# ntop -A
Please enter the password for the admin user: **********
Please enter the password again: **********

vyatta:~# /etc/init.d/ntop start

vyatta:~# /etc/init.d/ntop stop

vyatta:~# killall ntop

vyatta:~# update-rc.d -f ntop remove

vyatta:~# update-rc.d ntop defaults 99 99

When done you should be able to connect to http://routers-ip:3000
From what I noticed the interface which will be listened on will be the external (eth0_) while you connect to the internal (eth1_).

By |How-To, Software, Technical|Comments Off on Vyatta Network Stats (NTOP) Install

Welcome to Google Voice

Google Voice, the popular and often controversial VoIP, voicemail, and messaging service from Mountain View search giant Google is now open for anyone in the U.S. to use. Previously, you could only open a Google Voice account if you received an invitation from a user already participating in the program.

Quote from the people at Google:

“We’re proud of the progress we’ve made with Google Voice over the last few years, and we’re still just scratching the surface of what’s possible when you combine your regular phone service with the latest web technology. It’s even more amazing to think about how far communication has come over the last couple hundred years”

To sign up for Google Voice, click here

Here are some things you can do to get started with Google Voice:

  1. Read transcriptions of voicemails. Watch a video »
  2. Customize which phones ring. Watch a video »
  3. Personalize greetings for different callers. Watch a video »
  4. Make cheap international calls. Watch a video »
  5. Forward SMS to email. Watch a video »
  6. Share voicemails with friends. Watch a video »
  7. Block unwanted callers. Watch a video »
  8. Screen callers before answering. Watch a video »
  9. Access the mobile app on your phone. Watch a video »
  10. Conference call with co-workers. Watch a video »
By |News, Technical|Comments Off on Welcome to Google Voice

Google SSL – Privacy I believe in

Today I got wind of a new beta from Google.  Google search over SSL.  Now you can have an end to end search that is encrypted between your computer and our friends over at Google.  This will protect your search terms and results from third parties such as your ISP, or company network admins who may be monitoring your search terms.   Stop over at https://www.google.com and give it a try.  Note:  HTTPS is for secure.

By |Personal, Technical|Comments Off on Google SSL – Privacy I believe in