Sponsored Content
Top Forums UNIX for Advanced & Expert Users How do I enable RSA authentication (i've already read the FreeBSD handbook on this... Post 34568 by xyyz on Thursday 27th of February 2003 08:12:16 PM
Old 02-27-2003
i'm still having issues.

i use putty to access my freebsd machine. i also used puttygen to create
a DSA keypair.

i coped the public key onto ~/.ssh/authorized_keys2 and the private on to
the usb flash device under id_dsa.

when i point putty to the private keypair, i get the following error:

"Server refused our key"

any clues how to sort this out?
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Clearify what it means under 'WHAT' when hit the 'w'-command

I wonder how I shall read the result below, especially 'what' shown below. The result was shown when I entered 'w'. E.g what is TOP? What is gosh ( what does selmgr mean?)? login@ idle JCPU PCPU what 6:15am 7:04 39 39 TOP 6:34am 6:45 45 45 TOP 6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies

2. IP Networking

BELKIN 'F5D5020' 16bit PCMCIA - FreeBSD HOWTO

Hey all, I've bought a few bits from Belkin who seem quite happy to support FreeBSD! Last time I bought a UPS from them and it's still going well :D I saw this on their website that the 16bit PCMCIA card was supported under FreeBSD: http://www.belkin.com/network/F5D5020.html I went to my... (0 Replies)
Discussion started by: WIntellect
0 Replies

3. UNIX Desktop Questions & Answers

FreeBSD 4.7 X issues - assistance req'd please

question: i just installed FreeBSD 4.7 on my laptop, when i log in as root, i can startx no problem at all but when i try to start it as a user, i can't. otiginally it told me i needed to be a member of the group 'wheel' to do startx, no problem, added myself in /etc/group, but for some reason i... (1 Reply)
Discussion started by: Calum
1 Replies

4. UNIX for Advanced & Expert Users

How to remove a file with a leading dash '-' in it's name?

Somehow someone created a file named '-ov' in the root directory. Given the name, the how was probably the result of some cpio command they bozo'ed. I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies

5. Shell Programming and Scripting

What are the differences between 'bash' and 'sh'

Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies

6. UNIX for Advanced & Expert Users

ssh RSA authentication failure

I am using an ssh pub key on two remote servers to allow ssh session without authentication. Both servers have the same id_rsa.pub copied from the host into the remote servers ~user/.ssh/authorized_keys. There is no passphrase for this key either. The problem is that I am able to ssh into one... (2 Replies)
Discussion started by: prkfriryce
2 Replies

7. UNIX for Dummies Questions & Answers

SSH with RSA keys - error contacting the authentication agent

Hi all, Basic Requirement: To SFTP large files (usually 10GB). We use webMethods 6.1.2 (installed on Unix) as the orchstrator and make underlying Unix system calls to do the processing. That is, if we have to SFTP a large file - webMethods will invoke a Perl script on the underlying Unix... (2 Replies)
Discussion started by: sandeeppotdar
2 Replies

8. Shell Programming and Scripting

Password-less RSA Authentication not working

Hello Friends, I know this issue has been raised many times and hence I tried every resolution provided in the forum before I posted this issue again. My Password-less RSA authentication was working fine for quite some time. Whenever the remote server password used to change I used to re-do... (5 Replies)
Discussion started by: mehimadri
5 Replies

9. BSD

How to enable FreeBSD 4.11 audits service?

Dear all My FreeBSD is version 4.11, I want to enable audit, Can anyone has a step by step document ? In FreeBSD.org I see the doc look like need recompile kernel? Is it really..? Thanks and happy new years. (0 Replies)
Discussion started by: nnnnnnine
0 Replies
Mono(sn)																  Mono(sn)

NAME
sn - Digitally sign/verify/compare strongnames on CLR assemblies. SYNOPSIS
sn [-q | -quiet] [options] [parameters] DESCRIPTION
Digitally sign, verify or compare CLR assemblies using strongnames. You can use the sn command to create "snk files" using the -k option described below. CONFIGURATION OPTIONS
Configuration options are stored in the machine.config configuration file under /configuration/strongNames. -c provider Change the default CSP (Crypto Service Provider). Currently not supported in Mono. -m [y|n] Use a machine [y] key container or a user [n] key container. Currently not supported in Mono. -Vl List the verification options. The list is kept under /configuration/ strongNames/verificationSettings in machine.config. -Vr assembly [userlist] Exempt the specified assembly from verification for the specified user list. Currently not supported by sn. You must edit machine.config manually if you require this. -Vu assembly Remove the exemption entry for the specified assembly. Currently not supported by sn, you must edit machine.config manually if you require this. -Vx Remove all exemptions entries. Currently not supported by sn, you must edit machine.config manually if you require this. CSP RELATED OPTIONS
-d container Delete the keypair present in the specified key container. -i keypair.snk container Import the specified strongname file into the specified container. -pc container publickey Export the public key from the specified CSP container to the specified file. CONVERSION OPTIONS
-e assembly output.pub Export the assembly public key to the specified output file. -p keypair.snk output.pub Export the public key from the specified strongname key file (SNK) or from a PKCS#12/PFX password protected file to the specified output file. -o input output.txt Convert the input file to a CSV file (using decimal). -oh input output.txt Convert the input file to a CSV file (using hexadecimal). STRONGNAME SIGNING OPTIONS
-D assembly1 assembly2 Compare if assembly1 and assembly are the same exception for their signature. This is done by comparing the hash of the metadata of both assembly. -k [size] keypair.snk Create a new strongname keypair in the specified file. The default key length is 1024 bits and MUST ALWAYS be used when signing 1.x assemblies. Any value from 384 to 16384 bits (in increments of 8 bits) is a valid key length to sign 2.x assemblies. To ensure max- imum compatibility you may want to continue using 1024 bits keys. Note that there's no good reason, even if it's possible, to use length lesser than 1024 bits. -R assembly keypair.snk Re-sign the specified assembly using the specified strongname keypair file (SNK) or a PKCS#12/PFX password protected file. You can only sign an assembly with the private key that match the public key inside the assembly (unless it's public key token has been remapped in machine.config). -Rc assembly container Re-sign the specified assembly using the specified strongname container. -t file Show the public key token from the specified file. -tp file Show the public key and the public key token from the specified file. -T assembly Show the public key token from the specified assembly. -Tp assembly Show the public key and the public key token from the specified assembly. -v assembly Verify the specified assembly signature. -vf assembly Verify the specified assembly signature (even if disabled). HELP OPTIONS
-h , -? Display basic help about this tool. -h config , -? config Display configuration related help about this tool. -h csp , -? csp Display Cryptographic Service Provider related help about this tool. -h convert , -? convert Display conversion related help about this tool. -h sn , -? sn Display strongname related help about this tool. CONFIGURATION FILE
Strongnames configuration is kept in "machine.config" file. Currently two features can be configured. /configuration/strongNames/pubTokenMapping This mechanism lets Mono remap a public key token, like the ECMA token, to another public key for verification. This is useful in two scenarios. First, assemblies signed with the "ECMA key" need to be verified by the "runtime" key (as the ECMA key isn't a public key). Second, many assemblies are signed with private keys that Mono can't use (e.g. System.Security.dll assembly). A new key can- not be used because it should change thr strongname (a new key pair would have a new public key which would produce a new token). Public key token remapping is the solution for both problems. Each token must be configured in a "map" entry similar to this one: <map Token="b77a5c561934e089" PublicKey="00..." /> /configuration/strongNames/verificationSettings It is often useful during development to use delay signed assemblies. Normally* the runtime wouldn't allow delay-signed assemblies to be loaded. This feature allows some delay-signed assemblies (based on their public key token, optionally assembly name and user name) to be used like they were fully signed assemblies. [*] Note that Mono 1.0 "runtime" doesn't validate strongname signatures so this option shouldn't be required in most scenarios. AUTHOR
Written by Sebastien Pouliot COPYRIGHT
Copyright (C) 2003 Motus Technologies. Copyright (C) 2004 Novell. Released under BSD license. MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-list for details. WEB SITE
Visit http://www.mono-project.com for details SEE ALSO
secutil(1) Mono(sn)
All times are GMT -4. The time now is 03:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy