Myside's Spew - Blog of Spontaneous Combustible Spew

Samsung Intercept FB01 2.2.3 Update Breaks Bluetooth

13 March, 2012 18:36 CST6CDT

Samsung started to push out an Android update in late February.  I received the update just a few days ago.  The Android update, FB01 for the Sprint Samsung Intercept updates the Android version from 2.2.1 to 2.2.3 and also updates the baseband (modem firmware), among other various fixes and patches.

It has been speculated by other websites that the intention was to remove the Carrier IQ software.  Unfortunately the update breaks 3rd party application access to the phone's Bluetooth resources.  Built in Bluetooth profiles such as OBEX file transfers and BT Audio for wireless headsets continued to work as it should.

I have several applications that need extended connections or administrative access to the Bluetooth resources.  Therefore I needed to revert to the stock 2.2.1 ROM or a 3rd party ROM and trick the Samsung update servers to show that the phone had been patched.  If this is not done, the update will continue to nag and annoy you with notifications of an update no matter if you are not using a stock Intercept ROM.

I decided to use a 3rd party ROM, however the stock 2.2 ROM is available on the Internet and is installable using the CM01 recovery tool.  Your phone needs to be rooted.  You may be able to do a factory reset as well to revert.  I do suggest flashing the new baseband firmware.

The file build.prop is located in the root /system folder after the Intercept update S:M910.05 S.FB01.  Any ROM, reverted Android version, or the like, may use the build properties section of this file to be copied and pasted in replacement to this section in your chosen Android alternative.  The section with the current phone build properties is located between "# begin build properties" & "# end build properties.".  Do not modify anything below these separators.

I have no information if or when the Intercept's 2.2.3 Bluetooth problem will be addressed by Samsung or Sprint.  I was not able to find an alternative solution in a reasonable amount of time.

edited 2012-03-15

Samsung Intercept (SPH-M910) related binary applications/utilities, miscellaneous resources, and ROMS may or may not be available here: Samsung Intercept

 

A year ago I was writing...

Updating Live: Japanese Earthquake and Nuclear Reactors
RCA ANT806 Reviewed - High Performance Universal Amplified Indoor/Outdoor Antenna
It is squirrel Thursday! - Evil Fur Kills Resistance
Problematic Social Structure of Thought - Mindsets see free as of: no quality, quantity, or value
HOWTO Tip - Waterproof your Smartphone

Software  Projects  Article & Comments

Current & Updating Webalizer Search Engine List

02 February, 2012 06:40 CST6CDT

as of 2012-02-02

The Webalizer is a HTTP server log analyzer that generates HTML visual output statistics with graphs about Internet websites and its visitors.  One of the many features of The Webalizer is its search engine query (keywords) referral logging.  Each search engine uses a URL parameter that contains the search query the Internet party or person used to be directed to a resource on you web server.  Webalizer uses the search query keywords to generate one of several reports that may be viewed and referenced.

This article contains a current list of search engines and parameters for Webalizer's SearchEngine parameter.  Feel free to add or modify a search engine (SearchEngine) for The Webalizer search engine query parsing in the comments.

SearchEngine    aolsearch.      q=
SearchEngine    ask.com q=
SearchEngine    bingj.  q=
SearchEngine    bing.   q=
SearchEngine    facebook.       q=
SearchEngine    google. q=
SearchEngine    image.youdao.com        q=
SearchEngine    kvasir.no       q=
SearchEngine    m.yahoo.        p=
SearchEngine    search.alot.    q=
SearchEngine    search.aol.     q=
SearchEngine    search.aol.     query=
SearchEngine    search.comcast.net      q=
SearchEngine    search.conduit. q=
SearchEngine    search.lycos.   query=
SearchEngine    search.pro      q=
SearchEngine    search.yahoo.   p=
SearchEngine    webcache.googleusercontent.com  q=
SearchEngine    altavista.com   q=
SearchEngine    eureka.com      q=
SearchEngine    hotbot.com      MT=
SearchEngine    msn.com         MT=
SearchEngine    infoseek.com    qt=
SearchEngine    webcrawler      searchText=
SearchEngine    excite          search=
SearchEngine    netscape.com    search=
SearchEngine    mamma.com       query=
SearchEngine    alltheweb.com   query=
SearchEngine    northernlight.com  qr=
SearchEngine    sensis.com.au   find=

Software  Projects  Article & Comments

Postfix TLS Fingerprints for MTA to MTA Identification

28 January, 2012 06:39 CST6CDT

edited 2012-01-28 11:30:43

I have a home mail server with a Linux operating system & Postfix that is the primary mail exchange (MX) for its domain.  In addition to the primary MTA, I have a static secondary relay mail server with a FreeBSD operating system & Postfix in the case my home connection were to go down.  I was looking for a way that my secondary or primary MTA (mail transport agent) could relay e-mail to my legitimate dynamic IP address if my home mail server were to go down by doing a verification that my dynamic domain name IP address with an open port 25 was truly its relay destination.

I accomplished simple MTA to MTA verification using Postfix, which is installed on both servers, and my home TLS certificate's fingerprint.  When my backup mail exchange server receives mail, it will relay it to my dynamic home server when it becomes available, though will only be delivered if my home TLS MD5 certificate fingerprint is valid.  If the MD5 fingerprint expected does not match, it is deferred, re-queued, and repeats indefinitely until it is safe to deliver.

The first step is to do a MD5 fingerprint on your home, dynamic Postfix server's TLS PEM file defined in the Postfix main.cf configuration file with the variable smtpd_tls_cert_file=/path/to/ssl-cert.pem using the openssl command:

openssl x509 -noout -in /path/to/ssl-cert.pem -fingerprint -md5

Let's assume the MD5 fingerprint output is: d5:68:da:c4:cd:ee:0d:ba:3a:bc:dd:b6:7b:67:51:88 and our dynamic domain name is domain.not.  Let's also assume the home mail server is setup and ready to receive e-mail for this domain and your users.

On your secondary and static backup MX server, make sure that domain.not is defined in the following parameters:

  • relay_domains=domain.not
  • relay_recipient_maps = hash:${config_directory}/relay_recipient_maps.cf

The configuration file relay_recipient_maps.cf contains a table of your recipients and may look like the following:

first.last@domain.not     first.last@domain.not

Make sure to execute: postmap /etc/postfix/relay_recipient_maps.cf or replace /etc/postfix with your configuration directory.

Your "transport_maps=" may look something like the following:

domain.not   smtp:[domain.not]

If your ISP blocks port 25, you may use the following for port 26, or any upper number port that is open and available:

domain.not smtp:[domain.not]:26

Now that we have the MD5 fingerprint of our home server and the static backup server knows what e-mail to accept and where to deliver it when your home server is up, we may now define in Postfix to only deliver mail if when requested the home Postfix server shows its certificate, and the MD5 fingerprint of the certificate matches.

First tell Postfix to use MD5 hashes for TLS policies: smtp_tls_fingerprint_digest = md5  Next, define your TLS policy configuration file, smtp_tls_policy_maps = hash:${config_directory}/tls_policy.cf

Here is an example SMTP TLS policy map:

[domain.not] fingerprint
    match=d5:68:da:c4:cd:ee:0d:ba:3a:bc:dd:b6:7b:67:51:88

In the above TLS policy, domain.not requires TLS and the MD5 fingerprint of the certificate must match, match=  Be sure to postmap the tls_policy.cf file, reload postfix, and you will now be using simple, low level MTA to MTA identification.

Software  Projects  Article & Comments

Javascript Flash Text

10 August, 2011 04:19 CST6CDT

The HTML 'Blink' element is quickly making its way out of the web browser rendering engines.  IE (Internet Explorer) ignores this element and will only display the text you want flashing as a normal textual output with no decorations.

I put together an easy script which will modify a CSS DIV ID's text to flash on and off at an interval of your choosing using Javascript.  Here is the example:

<html>
<head>
<script type="text/javascript">
var i=0;
function flashtext() {
if(i%2==0)
{ var textcolours = 'black'; }
else
{ var textcolours = 'white'; }
document.getElementById( 'flashingtext' ).style.color = textcolours;
if(i<1)
{ i++; }
else
{ i-- }
}
setInterval( 'flashtext()', 500 );
</script>
</head>

<body>
<div id="flashingtext">this text will flash</div>
</body>
</html>

If you need to turn on or off the textual flashing using an OnClick type method, you may assign an ID to setInterval() and then clear that interval using clearInterval();  For example, remove "setInterval( 'flashtext()', 500 );" from the above Javascript and fill an <a> tag with "ft = setInterval( 'flashtext()', 500 );" to execute the flash function identified by 'ft', and then you may optionally clear the flashing text intervals with "clearInterval ( ft );" using the examples below:

<a href="javascript:void(0)" onclick="ft = setInterval( 'flashtext()', 500 );">on link</a>

<a href="javascript:void(0)" onclick="clearInterval ( ft );">off link</a>

A year ago I was writing...

Verbatim SOHO NAS (96436) Firmware Update
.88 miles of track on my map

Software  Projects  Article & Comments

Lightweight WINS Server - LWINS

19 June, 2011 09:07 CST6CDT

I use a Cobalt RAQ (MIPS) for most of my general network services.  These services include DHCP, BIND (DNS), SMTP, NTP, and WINS.  I decided to look around to replace Samba's NMBD WINS service and came across the LWINS project.

LWINS is a lightweight WINS server capable of running on memory restricted devices and is independent from SAMBA. WINS implements the NetBIOS protocol over TCP/IP. LWINS also supports replication with MS-WINS servers. Robustness of the protocol stack is a very high priority so that malformed packets cannot be used to crash LWINS, or gain access to the machine running LWINS. However, the security of the network is limited as the protocols were not designed with security in mind.

The LWINS project states that the server is intended for OpenWRT (Linux), however it will compile on any platform with restricted resources making it a perfect candidate for my RAQ with 96MB of RAM running Debian Squeeze.  With a modification of the makefile, you should be able to successfully compile LWINS on ARM, MIPS, or any other architecture provided you have the basic general required libraries that are installed in most Linux, BSD, etc. operating systems and distributions.

Currently on my home network, LWINS is using a mere 708KB of RAM monitoring 6 computers or devices that take advantage of WINS and NetBIOS over TCP/IP.  My only suggestion would be to run this application as root commenting out the appropriate lines in the example configuration file provided as some OS installations prohibit management of privileged ports to unauthorized user accounts.

[http://www.lwins.org/]

A year ago I was writing...

Google Voice Call Me Button in Internet Explorer is Broken
BloGTK Ubuntu Lucid Lynx Dependency Fix: gtkhtml2 (python-gtkhtml2)
spamd line 2588 - Spamassassin 3.3
It is squirrel Thursday! - Jedi Squirrel Victorinox Pocket Knife
Essential Oils: Sage Dalmation & Bergamot

Software  Projects  Article & Comments (1)

1 2 3 4 5 6 7 8  Next»
Land where drunk cows swim and home to my daily hand