i still got the Problem, that my Java Interpreter can't handle SSL Handshake from a FTPS Client Connection. So I want to try out another FTPS Class that cann store a File on a FTP Server.
Do you know any other Examples/Classes than the Commons.Net one ?
Thank you, Louis
Related
I'm using the Socket class to upload a file over FTP to a server. I have been trying to figure out how to implement SFTP and I haven't found any library or API anywhere. But as I was working on it I saw a SecureSocket class. Is this SFTP or FTPS / TLS or something else?
Update:
It looks like it's SSL and TLS:
The SecureSocket class enables code to make socket connections using
the Secure Sockets Layer (SSL) and Transport Layer Security (TLS)
protocols.
Can I just switch to using this? Is this what I've been looking for all of my life?
SecureSocket is a TLS-protected socket. It's not related to SFTP (which is a protocol used on top of SSH, not TLS). SecureSocket can be used for FTP/TLS if you write an FTP client in ActionScipt - then you can use that socket.
I'm a newbie in stackoverflow and perl IO::Socket sockets programming and I have a problem with my project. I have a TCP client and server script where the client can send file to the server. The server side creates a directory where it stores the received received files.
Is it possible for me to view and retrieve/download the files that I have sent to the server?
My professor told me that if i could add these functions he would reconsider my project.
help would be greatly appreciated. THANK YOU!
A possible approach will be to send a "string" command to the server that will trigger the server to scan the download directory for all file by using the code below
The names of the files can then be sent by the server app back through the client socket
Subsequently another string command for download can be sent to the server indicating the file path of the file your're interested in and you'll use the same process you used to send the file to the server in the first place to send it back to the client.
I want to send APN (Apple Push Notification) from PHP script. My PHP script is working fine and I receive notification in the iphone device as well when sending from localhost but when I upload the same script with same .pem file to the shared server it returns error...
Warning: stream_socket_client() [function.stream-socket-client]: unable to connect to ssl://gateway.push.apple.com:2195 (Connection refused) in /mypath/SendPushNotification.php on line 28 Failed to connect: 111 Connection refused
From some source I get to know that to send APN port 2195 must be open which is not possible in the shared server plan. So I tried using dedicated server and it's working perfectly and I receive the notification on the device. I tried hard to find the solution for shared server but didn't find any solution.
My question: is it possible send APN without opening port 2195 from shared server? if Yes give some guidance.
No, Its not possible to send APN message without using 2195 port.
If you want to send push notification message from shared server, try using some third party tools like http://urbanairship.com/.
Some time ago I got the same error, and then I found that it ocurres because of the server, the proxy is blocking that port, because most of servers doesn't use that port as a common one(80 or 21).
In this case you could try asking for support on your server reseller , they can open that port (2195) for you, If your take this solution I would recommend also asking to open the port 2196 that port is used for feedback.
Another solution is to use a free push notification provider, like Parse which is really easy to use and implement on your app, also you can use UrbanAirship, but I preffer Parse ;)
Hope it helps
This is irritating and definitely port 2195 issue. Chat with your hosting provider and ask them to open the port. I also had same issue. My Local code was running peacefully in every condition like sandbox and production but it was failing on the server.
Dont get confused about .pem file path and that would be simple corresponding to your code. For me i put my certificates (.pem) in a directory named certs and gave path like this:
$apnsCert = 'certs/cert_prod.pem';
The code was not working on my apps production server. I wasted one and a half day on this but that ran great on first run when i put that on application's staging server. Reason!!!! Definitely port 2195 issue.
All the beat.
There is anyway to decrypt the FTP passwords stored on Netbeans (from PHP projects) on folder called "keyring", assuming that I have informations from my windows account ???
I had lost password of one of my ftp sites.
I tried to connect with Wireshark sniffing TCP connections.
and i managed to get back the lost password.
[WRONG ! See below] No, passwords are not "encrypted" but "hashed", which is a single-way operation.
EDIT: This answer is shamefully wrong, and sits here like this since 3 years. I am deeply sorry, I don't even know why I answered something so stupid.
An easy way to get back this password would be try to connect to a server using it and dumping it using Wireshark sniffing the TCP connection.
I have one audio file captured from my iphone. I want to upload this audio file using SFTP protocol?
Is is possible? Is there any third party library available? Is it the same as putting file on FTP?
Apple has a tech note on this subject.
http://developer.apple.com/iphone/library/technotes/tn2009/tn2152.html#SECFILETRANSFERPROTOCOLS
The following section discuses support for file transfer.
Note: There have been numerous attempts to make a secure 'FTP'.
These include:
FTPS — This is FTP over TLS. It is not supported by any built-in APIs on iPhone OS or Mac OS X.
SFTP — This is a new file transfer protocol based on SSH. There are no SSH APIs built in to either iPhone OS or Mac OS X. On Mac OS X you can access SSH functionality by sublaunching various command line tools. This is not an option on iPhone OS.
The SFTP and FTP are completely different protocols.
Basically, there are the following file transfer protocols around:
FTP – the plain old FTP protocol that has been around since 1970s. The acronym stands for "File Transfer Protocol". It usually runs over TCP port 21.
SFTP – another, completely different file transfer protocol that has nothing to do with FTP. SFTP runs over an SSH session, usually on TCP port 22. It has been around since late 1990s. The acronym actually stands for "SSH File Transfer Protocol".
FTPS or FTP/SSL - the plain, old FTP protocol run over TLS/SSL secure communication channel. FTP and FTPS relation is the same as HTTP and HTTPS relation to each other.
Secure FTP - depends on context. Sometimes means FTPS, sometimes SFTP.