Palm OS Wristwatch

countach writes "Amazon are taking orders for a new Palm OS Wrist Watch. It has an infra-red port, touch screen, back-light, stylus and 2MB of RAM. Price is $US 295.00." Because sometimes you don't look nerdy enough ;)

Comments

FOR SALE

[Anonymous Coward]

Murray mower w/ Briggs & Stratton motor

22"
4.0 hp
3 yrs old
new blade

$40

FIRST POST!!

Common practices

[Anonymous Coward]

The following list contains information regarding what types of encryption are used by specific security systems/functions/applications/protocols. Glaring security vulnerabilities with WEP are also listed.

WEP (Wired Equivalency Protection) - Uses a shared key, RC4 Encryption at 40, 64, 128, or 256 bit. The key is shared. Authentication is one way. Due to the design of RC4 (intended to be used over a synchronous stream), WEP designers have to make RC4 change the key for each packet. This means that the keys are quickly reused, and thus a sinffer can eventually - and usually rather quickly in large networks - determine the key loop. The SSID (Service Set ID) is sent over the wire either unencrypted or encrypted using weak algorithims.

VPN (Virtual Private Networking) - IPSec, PPTP, L2TP, SSH, and even SSL

TACACS/+ (Terminal Access Controller Access Control System) - Uses kerberos style authetication that does not require keys to be sent over the wire. Uses two factor authorization (what you know and what you own, or what you know and what you are)

SSH (Secure SHell) - RC4, 3DES, Blowfish, and AES-256. OpenSSH does not use any patented algorithims.

IPsec (Internet Protocol Security*) - Diffie-Hellman key exchange between peers on a network. Public key cryptography is applied to the Diffie-Hellman exchanges to safeguard against spoofing and man-in-the-middle attacks. IPSec uses standard algorithims such as DES for data encryption. Keyed (HMAC) and non-keyed (MD5, SHA) hasing for packet authentication. Signed digital certificates are used to provide proof of identity. TCP control packets are authenticated, preventing DOS attacks (such as those used against PPTP) that rely on TCP control packets.

Wear your PalmOS Watch on your Segway

[burgburgburg]

Be an uber-Geek!

Re:Wear your PalmOS Watch on your Segway

[Anonymous Coward]

Now you can shit your pants - twice!

Steve Jobs will really hate you then!

static methods for objective C?

[Anonymous Coward]

Gentlemen, In the world of C++, instance methods are static by default, unless made dynamic with the virtual keyword.

In Java, public and protected methods are dynamic by default (although private methods are static) unless made static with the final keyword.

In Objective-C, however, all methods are dynamic.

While offering run-time binding, this also leads to slower performance -- especially given that the run-time system must be queried for *every* message sent.

I propose that static instance methods be allowed. Here's how they would work:

• When the compiler knows the type of the object, it would call the function directly without doing a run-time method lookup. The symbol resolving would be done are link-time.
  
• If the compiler doesn't know the type of the object, it would do a run-time lookup as normal.
  
• When declaring and implementing classes, the compiler would prevent static methods from being overridden.
  
• static methods would not be valid in protocol definitions (they must be bound to a specific class)

I believe this could give a nice speed bump for methods where overriding is not desirable, or necessary, while retaining hte dynamic nature of objective-C.

Before I do a test-implementation, does anyone have any thoughts?