giovedì 24 dicembre 2009
mercoledì 23 dicembre 2009
lunedì 21 dicembre 2009
venerdì 4 dicembre 2009
giovedì 3 dicembre 2009
giovedì 29 ottobre 2009
PSCP.exe - Esempi vari - seconda parte
To receive (a) file(s) from a remote server:
pscp [options] [user@]host:source target
So to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type:
pscp fred@example.com:/etc/hosts c:\temp\example-hosts.txt
To send (a) file(s) to a remote server:
pscp [options] source [source...] [user@]host:target
So to copy the local file c:\documents\foo.txt to the server example.com as user fred to the file /tmp/foo you would type:
pscp c:\documents\foo.txt fred@example.com:/tmp/foo
You can use wildcards to transfer multiple files in either direction, like this:
pscp c:\documents\*.doc fred@example.com:docfiles
pscp fred@example.com:source/*.c c:\source
However, in the second case (using a wildcard for multiple remote files) you may see a warning saying something like ‘warning: remote host tried to write to a file called 'terminal.c' when we requested a file called '*.c'. If this is a wildcard, consider upgrading to SSH 2 or using the '-unsafe' option. Renaming of this file has been disallowed’.
This is due to a fundamental insecurity in the old-style SCP protocol: the client sends the wildcard string (*.c) to the server, and the server sends back a sequence of file names that match the wildcard pattern. However, there is nothing to stop the server sending back a different pattern and writing over one of your other files: if you request *.c, the server might send back the file name AUTOEXEC.BAT and install a virus for you. Since the wildcard matching rules are decided by the server, the client cannot reliably verify that the filenames sent back match the pattern.
pscp [options] [user@]host:source target
So to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type:
pscp fred@example.com:/etc/hosts c:\temp\example-hosts.txt
To send (a) file(s) to a remote server:
pscp [options] source [source...] [user@]host:target
So to copy the local file c:\documents\foo.txt to the server example.com as user fred to the file /tmp/foo you would type:
pscp c:\documents\foo.txt fred@example.com:/tmp/foo
You can use wildcards to transfer multiple files in either direction, like this:
pscp c:\documents\*.doc fred@example.com:docfiles
pscp fred@example.com:source/*.c c:\source
However, in the second case (using a wildcard for multiple remote files) you may see a warning saying something like ‘warning: remote host tried to write to a file called 'terminal.c' when we requested a file called '*.c'. If this is a wildcard, consider upgrading to SSH 2 or using the '-unsafe' option. Renaming of this file has been disallowed’.
This is due to a fundamental insecurity in the old-style SCP protocol: the client sends the wildcard string (*.c) to the server, and the server sends back a sequence of file names that match the wildcard pattern. However, there is nothing to stop the server sending back a different pattern and writing over one of your other files: if you request *.c, the server might send back the file name AUTOEXEC.BAT and install a virus for you. Since the wildcard matching rules are decided by the server, the client cannot reliably verify that the filenames sent back match the pattern.
PSCP.exe per copiare files su un server remoto. Esempi vari
A second method to transfer files from a Windows command line prompt is to use PSCP. Unlike PSFTP, PSCP is not interactive and is designed to transfer files "in one shot" and then exit, much like OpenSSH's scp command. PSCP also allows you to specify wildcards within filenames (PSFTP does not). Additionally, PSCP will work with any SSH server as it is not dependent on SSHv2 being present.
Note PSCP will blindly copy files to the remote server, overwriting any files with the same name, without prompting for verification. Be careful when using PSCP to copy files.
If you wish to prevent PSCP from overwriting any files, remove any write permissions on any file you wish to keep. This can be done on a UNIX system by issuing the following command:
$ chmod --w file
This will prevent PSCP from overwriting the file.
PSCP is run from the command line and has many options, which you can see via the –h option:
C:\>pscp -h
PuTTY Secure Copy client
Release 0.53b
Usage: pscp [options] [user@]host:source target
pscp [options] source [source...] [user@]host:target
pscp [options] -ls user@host:filespec
Options:
-p preserve file attributes
-q quiet, don't show statistics
-r copy directories recursively
-v show verbose messages
-load sessname Load settings from saved session
-P port connect to specified port
-l user connect with specified username
-pw passw login with specified password
-1 -2 force use of particular SSH protocol version
-C enable compression
-i key private key file for authentication
-batch disable all interactive prompts
-unsafe allow server-side wildcards (DANGEROUS)
Transfer files from the command line with PSCP
Some of the more common options are explained in more detail below:
-p = This will preserve the date and timestamps on any file transferred.
-r = By default, PSCP will only copy files and skip over any directories encountered. The –r option will recursively copy any directory structures encountered.
The following are two examples of utilizing PSCP to exchange files with machine server.example.com as user sshuser.
Click on the Start Menu and select Run. In the field provided, type in cmd if you are running Windows NT/2000/XP or command if you are running Windows 9x/ME and click on the OK button.
The syntax for downloading a file from a remote machine is as follows:
pscpuser@hostname:remote-filename local-filename
where user is the user ID to which you will connect on the remote machine, hostname is the hostname or IP address of the remote machine, remote-filename is the full path and name of the file on the remote machine to download and local-filename is the full path and name of the downloaded file.
It is not necessary to specify the directory for the remote-filename or target-filename arguments. If the directory is not specified in the remote-filename argument, PSCP assumes the file is in the remote home directory of the user ID that is specified. If the directory is not specified in the local-filename argument, PSCP will download the file into the current directory. However, both arguments are required, so if you do not wish to change the name of the downloaded file and you want to put it into the current local directory, specify "." for the local-filename argument. "." represents the current directory:
Here is an example of a user using PSCP to connect to machine server.example.com as user sshuser and downloading the file named test.pl to the current directory:
C:\>pscp sshuser@server.example.com:test.pl .
sshuser@server.example.com's password: ********
test.pl | 0 kB | 0.1 kB/s | ETA: 00:00:00 | 100%
C:\>
The syntax for uploading a file is as follows:
pscplocal-filename user@hostname:remote-filename
where user is the user to connect to on the remote machine, hostname is the hostname or IP address of the remote machine, local-filename is the full path and name of the local file to upload and remote-filename is the full path and name ofthe remote uploaded file. If no directory is specified for the local-filename argument, the current local directory will be used. If no directory is specified forthe remote-filename argument, the remote home directory of the user logging in will be used. However, the colon following the hostname must still be present.
Here is an example of a user using PSCP to connect to machine server.example.com as user sshuser and uploading all files named test.* to /tmp:
C:\>pscp test.* sshuser@server.example.com:/tmp
sshuser@server.example.com's password:
test.c | 0 kB | 0.1 kB/s | ETA: 00:00:00 | 100%
test.sh | 0 kB | 0.2 kB/s | ETA: 00:00:00 | 100%
C:\>
Note PSCP will blindly copy files to the remote server, overwriting any files with the same name, without prompting for verification. Be careful when using PSCP to copy files.
If you wish to prevent PSCP from overwriting any files, remove any write permissions on any file you wish to keep. This can be done on a UNIX system by issuing the following command:
$ chmod --w file
This will prevent PSCP from overwriting the file.
PSCP is run from the command line and has many options, which you can see via the –h option:
C:\>pscp -h
PuTTY Secure Copy client
Release 0.53b
Usage: pscp [options] [user@]host:source target
pscp [options] source [source...] [user@]host:target
pscp [options] -ls user@host:filespec
Options:
-p preserve file attributes
-q quiet, don't show statistics
-r copy directories recursively
-v show verbose messages
-load sessname Load settings from saved session
-P port connect to specified port
-l user connect with specified username
-pw passw login with specified password
-1 -2 force use of particular SSH protocol version
-C enable compression
-i key private key file for authentication
-batch disable all interactive prompts
-unsafe allow server-side wildcards (DANGEROUS)
Transfer files from the command line with PSCP
Some of the more common options are explained in more detail below:
-p = This will preserve the date and timestamps on any file transferred.
-r = By default, PSCP will only copy files and skip over any directories encountered. The –r option will recursively copy any directory structures encountered.
The following are two examples of utilizing PSCP to exchange files with machine server.example.com as user sshuser.
Click on the Start Menu and select Run. In the field provided, type in cmd if you are running Windows NT/2000/XP or command if you are running Windows 9x/ME and click on the OK button.
The syntax for downloading a file from a remote machine is as follows:
pscpuser@hostname:remote-filename local-filename
where user is the user ID to which you will connect on the remote machine, hostname is the hostname or IP address of the remote machine, remote-filename is the full path and name of the file on the remote machine to download and local-filename is the full path and name of the downloaded file.
It is not necessary to specify the directory for the remote-filename or target-filename arguments. If the directory is not specified in the remote-filename argument, PSCP assumes the file is in the remote home directory of the user ID that is specified. If the directory is not specified in the local-filename argument, PSCP will download the file into the current directory. However, both arguments are required, so if you do not wish to change the name of the downloaded file and you want to put it into the current local directory, specify "." for the local-filename argument. "." represents the current directory:
Here is an example of a user using PSCP to connect to machine server.example.com as user sshuser and downloading the file named test.pl to the current directory:
C:\>pscp sshuser@server.example.com:test.pl .
sshuser@server.example.com's password: ********
test.pl | 0 kB | 0.1 kB/s | ETA: 00:00:00 | 100%
C:\>
The syntax for uploading a file is as follows:
pscplocal-filename user@hostname:remote-filename
where user is the user to connect to on the remote machine, hostname is the hostname or IP address of the remote machine, local-filename is the full path and name of the local file to upload and remote-filename is the full path and name ofthe remote uploaded file. If no directory is specified for the local-filename argument, the current local directory will be used. If no directory is specified forthe remote-filename argument, the remote home directory of the user logging in will be used. However, the colon following the hostname must still be present.
Here is an example of a user using PSCP to connect to machine server.example.com as user sshuser and uploading all files named test.* to /tmp:
C:\>pscp test.* sshuser@server.example.com:/tmp
sshuser@server.example.com's password:
test.c | 0 kB | 0.1 kB/s | ETA: 00:00:00 | 100%
test.sh | 0 kB | 0.2 kB/s | ETA: 00:00:00 | 100%
C:\>
mercoledì 28 ottobre 2009
Spostare la cartella di Google su un altro volume (via regedit)
Google Desktop tip - move Google Desktop's search index to a different drive or folder
Why?
If the search index is getting too big, moving it to a new drive will free up some space on your main drive.
Instructions
A) Move folder
Click start, Run, and type %userprofile%\Local Settings\Application Data\Google\
Cut and paste the Google Desktop Search folder to a new location
B) Tell Google Desktop about the new location
Click start, Run, enter regedit and go to HKEY_CURRENT_USER\Software\Google\Google Desktop
Locate the string value called data_dir and change its value data to the new location
Restart Google Desktop
Why?
If the search index is getting too big, moving it to a new drive will free up some space on your main drive.
Instructions
A) Move folder
Click start, Run, and type %userprofile%\Local Settings\Application Data\Google\
Cut and paste the Google Desktop Search folder to a new location
B) Tell Google Desktop about the new location
Click start, Run, enter regedit and go to HKEY_CURRENT_USER\Software\Google\Google Desktop
Locate the string value called data_dir and change its value data to the new location
Restart Google Desktop
martedì 15 settembre 2009
Using DiskPart.exe As Disk Management Alternative in Windows Vista, 2000, 2003 and XP
Using DiskPart.exe As Disk Management Alternative in Windows Vista, 2000, 2003 and XP: "Using DiskPart.exe As Disk Management Alternative in Windows Vista, 2000, 2003 and XP"
venerdì 11 settembre 2009
giovedì 10 settembre 2009
domenica 23 agosto 2009
venerdì 31 luglio 2009
About | Daihinia
About | Daihinia: "The 'out-of-box' capabilities of 802.11 Ad-Hoc networking allows data to be sent and received only within the station's immediate range. In contrast to the classical definition of an Ad-Hoc Network, it does not relay packets further on.
The software developed here fills exactly this gap, providing an intermediate network layer between the WiFi network adapter and the upper protocols, allowing the protocols to communicate with any station in the network, not only with the immediate neighbors.
This project aims at creating a Mesh layer for WiFi Ad-Hoc networks, thus making the network infrastructure be implicitly maintained by the users themselves. It's a nice idea that a network user supports the network around him/her just by the fact that he/she uses the network.
Unlike other solutions that allow mesh topology only between access points, this software puts it diretly on client nodes. Given that it's based on WiFi's Ad-Hoc mode of operation, users don't need any access points at all to build and maintain their network!"
The software developed here fills exactly this gap, providing an intermediate network layer between the WiFi network adapter and the upper protocols, allowing the protocols to communicate with any station in the network, not only with the immediate neighbors.
This project aims at creating a Mesh layer for WiFi Ad-Hoc networks, thus making the network infrastructure be implicitly maintained by the users themselves. It's a nice idea that a network user supports the network around him/her just by the fact that he/she uses the network.
Unlike other solutions that allow mesh topology only between access points, this software puts it diretly on client nodes. Given that it's based on WiFi's Ad-Hoc mode of operation, users don't need any access points at all to build and maintain their network!"
sabato 25 luglio 2009
Iscriviti a:
Post (Atom)