It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
So I use lame to convert my files and they play fine on the machine. I used to scp them to another server and they would still play fine.
I started doing ftp, but un0converted wav files and the converted mp3 both sound very choppy once I transfer them...
Why would that happen?
FTP may be taken as an ancient protocol which normally works in ASCII mode to get file lists etc. According to protocol, we have to tell server change to binary mode before we get binary files. Looks like you are transferring files in ascii mode but all current ftp client apps I've known works in binary mode by default.
default transmission file of many ftp servers are "binary"
when you connect to a ftp server, server broadcast "transfer type"
if transfer type indicates "binary" check network connection
otherwise execute "bina" and change xfer mode to binary
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I'm trying to perform automation for transferring the file from Ubuntu(Linux) to Window system using python. I'm stuck with how I can implement this. Can anyone please suggest me a way to implement this.
My input for this will username, password, and windows path for the script.
You don't explain what transfer files mean, and if you want to transfer on the same computer (having a Windows file system and a Linux one on two different disk partitions) or on two different ones. You should think in terms of network communication protocols and file systems.
For remote file transfer, think in terms of network communication protocols : you might consider using rcp or scp or HTTPS or HTTP or rsync or to transfer the files (see this and that). Take into account cybersecurity considerations, so consider Python cryptographic services. You could also consider network file systems such as NFS or CIFS (a.k.a. SMB) or sshfs. HTTP and HTTPS and SSH protocols (both client and server side, look also into libssh) which is widely supported by Python or Guile bindings.
For local computer transfer between different disk partitions, think in terms of file systems, you could consider mounting the other's OS partition. Be then aware of VFAT or NTFS and CIFS support in Linux, and Ext2fs and NFS support on Windows.
You can code in Python (with pycurl and/or other Internet protocols) or Guile quite easily web services. Be aware of SOAP and REST (and SMTP to send emails). You could be interested by WebSockets to code a nice web interface. You may be interested by Python or Guile bindings to SMTP client libraries, HTTPS or libssh server or client libraries.
Consider also using distributed version control systems such as git - with a remote repository. Of course you'll find pygit2, a Python binding to it, and of course git is running both server side and client side on both Windows and Linux.
Be also aware of legal licensing considerations mentioned here.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I want to establish a secure communication between embedded devices. I am using TMS570 microcontroller and I have FreeRTOS running on it. So can you please provide me some guidelines regarding how I can implement SSL on it (preferably MatrixSSL /CyaSSL)
CyaSSL, and a demo application that demonstrates how to use it with FreeRTOS, are included in the official FreeRTOS zip file download.
The demo uses the FreeRTOS Windows simulator to ensure it is easily accessible without the need for any special hardware. Although the demo uses the Windows TCP/IP stack CyaSSL just needs a standards sockets interface, so if your TCP/IP stack has that (I can only think of one that doesn't) then the example integration is equally applicable to a TMS570 application.
Links to the main FreeRTOS/CyaSSL page and the documentation for the example are provided below:
1) http://www.FreeRTOS.org/ssl
2) http://www.freertos.org/FreeRTOS-Plus/CyaSSL/FreeRTOS_CyaSSL_Example.shtml
If you are building CyaSSL proper for FreeRTOS, you'll need to uncomment the define for FREERTOS in the /cyassl/ctaocrypt/settings.h file.
As Richard stated, CyaSSL uses the BSD socket API by default. I'm not sure what TCP/IP stack you are using, but a common TCP/IP stack to use with FreeRTOS and CyaSSL would be LwIP, in which case you would need to uncomment the CYASSL_LWIP define as well.
If your TCP/IP stack (or other transport medium) doesn't provide a BSD-style socket API, CyaSSL provides an I/O callback for applications to register their own I/O functions with CyaSSL. More information on this can be found in Chapter 5 of the CyaSSL Manual:
CyaSSL Manual (Chapter 5): http://yassl.com/yaSSL/Docs-cyassl-manual-5-portability.html
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I would suspect such a method might not even expose much from an engineering standpoint from the architecture and hence to not even be intrusive to the involved entity's intellectual property.
Probably not, because the JIT compiler would have to compile that code in real time first, and since drivers hook into the kernel, the kernel would be the only real program that could do that, and since this arrives the possibility of security issues I would imagine such a scenario would not be practical.
Another reason for that being impossible in general is that the internal kernel API is different, even conceptually, between Windows and Linux.
So in general a Windows driver is based on resources and functions that are Windows specific (and vice-versa).
Some clever people could do an ndiswrapper but I guess they had to simulate the Windows kernel specific API for wifi...; doing that for other types of drivers (graphics, ...) may be practically impossible.
A practical advice is to avoid buy hardware without Linux drivers (preferably free software ones). This put a market pressure on hardware manufacturers.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
There are a notebook A and a wireless access point B.
The scenario is:
1. the notebook A successfully connects to the wireless access point B.
2. the notebook A sends a "hello" message to my server.
3. my server receives this message. My question is how my server knows this message is sent by the notebook A (not other notebooks) via the wireless access point B (not via other wireless access points). Here who uses the notebook A is not my concern.
I am thinking a rough solution like this. Let my server know the notebook A's CPU serial number and the wireless access point's mac address. Any computer sending message to my server needs to report its CPU serial number and wireless gateway mac address. If these two are the same as those kept by my server, then pass.
I understand those two can be faked also. Please advise better solutions. Thank you so much.
Set up your access point to run WPA enterprise. Run the RADIUS server on your server. Optionally tunnel the traffic from the AP to the server. Issue unique credentials to each possible client, possibly certificate based.
With the RADIUS information and a "secure" (i.e. tunneled or direct cabled link) from the AP you can unambiguously and securely identify the wireless clients on the server, provided you trust the whole machine, the AP and the intermediate links.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I have a winCE device. I need to know whether the device has support for activesync. How can I check whether the device has support for ActiveSync?
Plug it in to a PC and see if the PC makes a connection?
Seriously, how, exactly, do you want to "check"? Programatically? Manually looking at the device? Some other way?
If you built the OS, it's in the catalog of the OS build.
If you didn't, then there's a file in the \Windows folder called "ceconfig.h" that outlines all of the SYSGENS used to build your OS, if it contains something like SYSGEN_AS_BASE or SYSGEN_AS_MAIL then at least some of the ActiveSync synchronization stuff was selected to be in the OS (though there are always ways to subvert the sysgen process, so it could still be missing, likewise it could also be there without the sysgen being defined). It would also bepresent in ce.bib, so if your OEM shipped you an NK.BIN and ce.bib, you could check that without even booting the device.
At runtime from an on-device app, you could look at the file system. The ActiveSync device-side piece is in repllog.exe, so it's presence in the \Windows folder would also be a strong indicator of inclusion in the OS.