[Tdg] Code commit

Alex Norman alex at neisis.net
Fri Mar 2 16:49:36 PST 2007 

use scp -r to send directories [recursively].

-ale

On  0, Graham Wakefield <wakefield at mat.ucsb.edu> wrote:
> actually, it looks like it is complaining about authorized_keys is a  
> file, not a directory, in my home dir on my own machine
> 
> i removed the file and replaced it with a directory
> 
> but then scp didn't work
> 
> is it supposed to be a file or a directory? does scp need some kind  
> of flag to make this work?  Sorry, I'm not experienced in console/ 
> unix stuff
> 
> Here's the terminal session:
> 
> g:~ grahamwakefield$ cd .ssh
> g:~/.ssh grahamwakefield$ ls
> id_rsa          id_rsa.pub      known_hosts
> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa
> Generating public/private dsa key pair.
> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ 
> id_dsa):
> Enter passphrase (empty for no passphrase):
> Enter same passphrase again:
> Your identification has been saved in /Users/grahamwakefield/.ssh/ 
> id_dsa.
> Your public key has been saved in /Users/grahamwakefield/.ssh/ 
> id_dsa.pub.
> The key fingerprint is:
> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield at g.local
> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub  
> wakefield at rails.mat.ucsb.edu: ~/.ssh/authorized_keys
> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory
> g:~/.ssh grahamwakefield$ ls
> authorized_keys id_dsa.pub      id_rsa.pub
> id_dsa          id_rsa          known_hosts
> g:~/.ssh grahamwakefield$ cd authorized_keys
> -bash: cd: authorized_keys: Not a directory
> g:~/.ssh grahamwakefield$ rm authorized_keys
> g:~/.ssh grahamwakefield$ ls
> id_dsa          id_dsa.pub      id_rsa          id_rsa.pub       
> known_hosts
> g:~/.ssh grahamwakefield$ mkdir authorized_keys
> g:~/.ssh grahamwakefield$ ls
> authorized_keys id_dsa.pub      id_rsa.pub
> id_dsa          id_rsa          known_hosts
> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub  
> wakefield at mat.ucsb.edu: ~/.ssh/authorized_keys
> The authenticity of host 'mat.ucsb.edu (128.111.92.3)' can't be  
> established.
> RSA key fingerprint is 51:41:15:67:75:99:e3:96:68:44:f3:91:5a:bd:53:ff.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'mat.ucsb.edu' (RSA) to the list of known  
> hosts.
> wakefield at mat.ucsb.edu's password:
> scp: .: not a regular file
> 
> 
> On Mar 2, 2007, at 4:19 PM, Jorge Castellanos wrote:
> 
> >You might have to create the .ssh directory in the home directory  
> >of the remote machine.
> >After this, you should be able to ssh without a password.
> >
> >
> >
> >
> >On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote:
> >
> >Hey Jorge -
> >
> >I'm stuck:
> >
> >g:~ grahamwakefield$ cd .ssh
> >g:~/.ssh grahamwakefield$ ls
> >id_rsa          id_rsa.pub      known_hosts
> >g:~/.ssh grahamwakefield$ ssh-keygen -t dsa
> >Generating public/private dsa key pair.
> >Enter file in which to save the key (/Users/grahamwakefield/.ssh/ 
> >id_dsa):
> >Enter passphrase (empty for no passphrase):
> >Enter same passphrase again:
> >Your identification has been saved in /Users/grahamwakefield/.ssh/ 
> >id_dsa.
> >Your public key has been saved in /Users/grahamwakefield/.ssh/ 
> >id_dsa.pub.
> >The key fingerprint is:
> >27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45  
> >grahamwakefield at g.local
> >g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub  
> >wakefield at rails.mat.ucsb.edu: ~/.ssh/authorized_keys
> >/Users/grahamwakefield/.ssh/authorized_keys: Not a directory
> >
> >?
> >
> >On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote:
> >
> >>Grahhhhhaaaaaammmm,
> >>
> >>Aqui va:
> >>
> >>1) Configure ssh to authenticate using dsa keys...
> >>
> >>	? Create a folder named ".ssh" in your home directory (if it  
> >>doesn't exist already)
> >>	? cd to the .ssh directory and type: "ssh-keygen -t dsa"
> >>	? it will ask for a paraphrase. Leave it blank (just press enter  
> >>through the three prompts)
> >>	? Copy the public key "id_dsa_[ub" to the .ssh directory in your  
> >>home directory of the remote machine (rails in this case) and  
> >>rename the file in the remote machine to "authorized_keys". You  
> >>can do these two steps using:
> >>	"scp ~/.ssh/id_dsa.pub user at targetServer.com: ~/.ssh/ 
> >>authorized_keys"
> >>
> >>* Note - Leaving the passphrase blank is not the most secure  
> >>thing, but that's the way it has to be for xcode and svnx to work.  
> >>As an alternative, you can use a key manager. I haven't use any,  
> >>but you could skip all the above and the manager would do all that  
> >>dynamically every time you connect. I think "SSHKeychain" does  
> >>that nicely in OSX. Never tried it though.
> >>
> >>Now you should be able to ssh to your account in rails without  
> >>entering any password.
> >>
> >>2) Configure SvnX
> >>	
> >>	? Open the "Repositories" window and create one. Fill the Path  
> >>field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ 
> >>tdg/svn/
> >>	? Double click the repository, and check it out. This should add  
> >>it to the "Working Copies" window. Now just use the working copy  
> >>to commit, update, etc...
> >>
> >>if I forgot something, please fill in...
> >>
> >>j
> >>
> >>
> >>
> >>
> >>
> >>On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote:
> >>
> >>For a svn newbie, could you step me through how you did this?  
> >>Muchas Gracias!
> >>
> >>On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote:
> >>
> >>>>If I can figure out my SVN client, I'll try and build an Xcode  
> >>>>project and add it.
> >>>
> >>>I've got it go work with SvnX. Using svn+ssh. For that to work  
> >>>you HAVE to configure password-less authentication (keygen...).
> >>>
> >>>j
> >>>
> >>>On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote:
> >>>
> >>>If I can figure out my SVN client, I'll try and build an Xcode  
> >>>project and add it.
> >>>
> >>>On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote:
> >>>
> >>>>Ok.. It builds & runs.. The code base has been committed to  
> >>>>subversion repo.
> >>>>
> >>>>Heres what's there:
> >>>>- New event stuff
> >>>>- Minimal application & scheduler
> >>>>- Placeholders for event queue, mem pool, etc.
> >>>>- Core_easy as a separate library
> >>>>- Example system library (graphics)
> >>>>- Example app (test_app)
> >>>>- Visual Studio solutions + projects
> >>>>- lots of other stuff we discussed.
> >>>>
> >>>>The stuff is in the repository under:
> >>>> \core\branch\mint
> >>>>
> >>>>The libs build a run in VS. I doubt it will build in gcc.. but  
> >>>>probably not far off.
> >>>>
> >>>>Rama
> >>>>
> >>>>_______________________________________________
> >>>>Tdg mailing list
> >>>>Tdg at mat.ucsb.edu
> >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >>>
> >>>_______________________________________________
> >>>Tdg mailing list
> >>>Tdg at mat.ucsb.edu
> >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >>>
> >>>_______________________________________________
> >>>Tdg mailing list
> >>>Tdg at mat.ucsb.edu
> >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >>
> >>_______________________________________________
> >>Tdg mailing list
> >>Tdg at mat.ucsb.edu
> >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >>
> >>_______________________________________________
> >>Tdg mailing list
> >>Tdg at mat.ucsb.edu
> >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >
> >_______________________________________________
> >Tdg mailing list
> >Tdg at mat.ucsb.edu
> >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >
> >_______________________________________________
> >Tdg mailing list
> >Tdg at mat.ucsb.edu
> >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> 
> _______________________________________________
> Tdg mailing list
> Tdg at mat.ucsb.edu
> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg

More information about the Tdg mailing list