Hi there,
I’ve exported this blog into my new one: http://darranboyd.wordpress.com or you can access it via www.darranboyd.com
For RSS use: http://darranboyd.wordpress.com/feed/
Thx
Hi there,
I’ve exported this blog into my new one: http://darranboyd.wordpress.com or you can access it via www.darranboyd.com
For RSS use: http://darranboyd.wordpress.com/feed/
Thx

Problem: I’ve got an iPhone 3G running 3.1.2(7D11) and I use a WLAN network at our office which does not broadcast it’s SSID for obscurity security reasons. Since some version, I guess 3.1, when I get within range of the SSID hidden network it no longer auto connects. Frustrating.
Solution: Apple to fix it in the next version I guess.
“Work around”: Not really a workaround, but a sightly less frustrating way of reconnecting… when in range of the network… recreate the network by entering the SSID and leave out any of the security stuff then click Join. The join will fail (for obvious reasons), but will then “remind” the phone that that network exists and will then connect using the previously configured settings.
Firstly, these tables go a long way towards showing the differences: Comparison between SFTP, FTP and SCP & Secure FTP, FTP/SSL, SFTP, FTPS, FTP, SCP… What’s the difference?
Here are some of my notes explaining the differences between these protocols:
SFTP (SSH file transfer) protocol
>Draft protocol designed by the IETF SECSH working group, working documents available here. RFC not complete.
>The protocol assumes that it runs over a secure channel, that the server has already authenticated the client, and that the identity of the client user is available to the protocol.
>The secure channel could be provided by SSH, TLS or others.
>When used with the SSH2 Protocol suite, this protocol is intended to be used as a subsystem as described in RFC4254 in the section “Starting a Shell or a Command”. The subsystem name used with this protocol is “sftp”.
>The SFTP protocol does more than just file transfer, including resuming interrupted transfers, directory listings, and remote file removal.
>From version 4 upwards this protocol has become more platform independent.
>Is a secure variant of rcp
>The protocol itself does not provide authentication and security; it relies on the underlying protocol, SSH, to provide these features.
>Does file transfer only,but does include file attributes (permissions, timestamps) – which is not possible with standard FTP.
>Mostly used on UNIX platforms, and seldom found on others.
>Note that many scp *programs* actually use SFTP (SSH file transfer) protocol instead.
FTPS (FTP Secure, FTP-SSL)
>Is an extension to the commonly used File Transfer Protocol (FTP) that adds support for the Transport Layer Security (TLS) and the Secure Sockets Layer (SSL) cryptographic protocols.
> RFC 4217 “Securing FTP with TLS” & RFC 959 “FTP Security Extensions”
FTP over SSH
>This is the act of using the standard FTP protocol over an already established SSH tunnel.
>Because FTP uses multiple TCP connections, it is particularly difficult to tunnel over SSH. With many SSH clients, attempting to set up a tunnel for the control channel (the initial client-to-server connection on port 21) will protect only that channel; when data is transferred, the FTP software at either end will set up new TCP connections (data channels) which will bypass the SSH connection.
I have been interested in creating a living room music-on-demand setup for our home for quite some time. One of my colleagues has been preaching to me that Sonos is the answer for a year or so now – but I’ve never really considered it because of it’s high cost of entry (~$999+). Recently, Sonos released a free iPhone/iPod touch remote control application. This allows a significantly less expensive entry cost, as now you only need to purchase a single Sonos ZonePlayer to get started… but I still felt that it was a be expensive (~$350)… especially when you compare it to using the AirTunes capability of the Apple AirPort express (~$99).
This past weekend he was kind enough to allow me to test out one of his Sonos ZonePlayers. The loan unit I had was a ZonePlayer ZP80, which is no longer being sold, but has been replaced with the ZP90 which now supports 802.11N. Neither the ZP80 nor ZP90 have internal amplifiers, so if you don’t have an amplifier you would need to consider the ZP120 (~$499).
So here are my brief thoughts and comments regarding the differences, pros and cons of the two solutions, and I’ll assume you already have the following (or workable equivalents):
Apple AirTunes
What you’ll need:
Setup is rather simple, just need to ‘authorize’ the iPhone remote app to connect to our iTunes library.
Pros:
Cons:
Sonos:
What you’ll need:
Pros:
Cons:
Conclusion:
I definitely enjoyed the experience of the Sonos solution more. There are many small, often unquantifiable, nuances that make it a more complete and enjoyable experience. The Apple AirTunes solution I described is workable, but not perfect.
If money was no object, then Sonos all the way, but unfortunately money is a big consideration. For now I’m going to hold onto these facts I’ve learnt – then see if I can convience myself to take the dive.
eBuddy appears to be the first free multi-protocol IM client for iPhone 3.0 with push notifications. The client supports MSN messenger, Yahoo! messenger, AIM, GTalk, Facebook and ICQ. I’ve confirmed it to work with GTalk on 3G/GPRS & WiFi… but there is one catch, it will only work for a maximum of 30mins after you close the application.
Do note that the application signs you out immediately by default, hence rendering the push notifications useless, so be sure to set the app to only sign you out after 30mins (max).
FYI – Appadvise.com are maintaining a list of all apps that support push notifications – check it out here
Install this: libflashsupport from Synaptic
Recent Comments