This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have been following the forums for about an year but haven't made an account for some reason.
I have the following struggle.
I am making a Blackberry application which uses networking - the standard j2me interfaces are used in blackberry development too.
I have to make a connection to a virtual private network(vpn).
For blackberry i found info claiming that you have to create a vpn account on the device manually then set it for a wifi connection and then your code will work.
I was wondering is it possible (if I know the authentication information for the vpn server I will be accessing) to pass that info over a ssl or some other connection(javax.microedition.io.SecureConnection or something similar i am not sure) and do the authentication behind the scenes and not to have to make the user set up a vpn account on the blackberry device ?
Sorry if this is a duplicate thread.
If it is not clear ask me to clarify what i am trying to do
Welcome to the JavaRanch, Alexsandar! Even though you've been here a while!
VPN and SSL aren't quite the same thing. On a VPN, you login once and the vpn interface wraps all of the cliient's outgoing traffic for that network in an ssh tunnel transparently. A lot of the time, the unwrapping of that network traffic is done by networking hardware, such as a Cisco router, so that back at the data center, the traffic is not encrypted on the LAN, just on the open Inernet.
With SSL/TLS, traffic is explicitly encrypted end-to-end, whether it's on the open Internet or in the LAN. The endpoint systems do the encryption and decryption. They also maintain their own private set of security credentials that are completely independent of any VPNs that their traffic might run through.
There's also a third option, which is "ssh tunnelling". This is a sort of poor person's VPN where only a single network port is encrypted using SSH. One of its most popular uses is to allow secure use of the X Window system on a remote client, since X works using (normally) unencrypted data on tcp/ip port 6000 and thus is a security risk, since it's how remote users can issue system commands and view data.
I routinely use ssh tunnelling to allow my local database support software to directly access databases in secure remote facilities.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jan 27, 2011
Thanks for the reply!
Its a great starting material on some networking topics.
It helped me to clarify some info and to know better what to look for.
Any ideas how I can make a connection through a proxy server with j2me?