Configure SSH Server on DragonFlyBSD After First Time Installation

I used to access server via ssh after first time installation of an server and since I use ‘common’ IP then I get famous message.

Get rid of that message :

$ ssh-keygen -f "/home/alamsyah/.ssh/known_hosts" -R 192.168.1.200
/home/alamsyah/.ssh/known_hosts updated.
Original contents retained as /home/alamsyah/.ssh/known_hosts.old

Then I try ssh

$ ssh [email protected]
The authenticity of host ‘192.168.1.200 (192.168.1.200)’ can’t be established.
ECDSA key fingerprint is 25:e4:32:fb:04:35:f8:63:fb:28:d9:55:2d:51:1e:8d.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.1.200’ (ECDSA) to the list of known hosts.
Permission denied (publickey).
$

Ups, Permission denied.

After google and read manual I got solution for editing ssh configuration

configure_ssh_dflybsd_1

Yes, ee is exist here in case you wondering about text editor here 🙂

config_ssh_dflybsd_2

Change “PasswordAuthentication” value from no to yes and save the file starting by press ESC button.

Restart ssh service

config_ssh_dflybsd_3

Retry ssh access from terminal or putty

$ ssh [email protected]
[email protected]’s password:
Last login: Thu Jan 16 11:24:46 2014
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
The Regents of the University of California.  All rights reserved.

DragonFly v3.6.0-RELEASE (GENERIC) #10: Sun Nov 24 07:57:21 PST 2013

Welcome to DragonFly!

Having trouble using fetch through a firewall?  Try setting the environment
variable FTP_PASSIVE_MODE to yes, and see fetch(3) for more details.
> su
Password:
dflybsd#

Great. This step give me more confident to explore the machine.

Install DragonFlyBSD part 2

At previous post I already show about requirement and installation steps of DragonFly BSD till configure area. In this post I’ll continue with Configuration of system. Lets get start.

DragonFly BSD provide the options via ‘sysinstall’ looks like interface as seen on this picture.

install_dflybsd_15

Configure TimeZone

Click on “select timezone” to configure timezone.

Continue reading

Install DragonFlyBSD part 1

Since first release I always want to try how DragonFlyBSD work. DragonFlyBSD that I call DFLYBSD is FreeBSD 4.8 version that evolved into new operating system with their own filesystem called HammerFS but of course UFS still supported.
I have spare time and want to install latest version (in time of writing I download version 3.6.0) on my VirtualBox under Ubuntu 13.04 Desktop.

So here we go :

1. Download latest version from here.

2. Create Space on VirtualBox with memory 512MB and 10GB hard disk plus bridge ethernet connection.

3. Use CD connect to iso file and start the machine.

install_dragonflybsd_1

Type ‘installer’ and hit Enter button.

Continue reading

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

2013 will pass and I want to learn new operating system and use this blog as place of documentation of my learning. OpenBSD is my choose and perhaps NetBSD too. How to get it up and many more. Today I’ve install OpenBSD using VirtualBox under Ubuntu Linux 13.04. Error message came out when I try to ssh newly install OpenBSD box :

$ ssh [email protected]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ba:4b:ee:4c:b1:6d:02:41:62:e0:19:1e:c5:11:e7:0b.
Please contact your system administrator.
Add correct host key in /home/alamsyah/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/alamsyah/.ssh/known_hosts:19
remove with: ssh-keygen -f “/home/alamsyah/.ssh/known_hosts” -R 192.168.1.207
ECDSA host key for 192.168.1.207 has changed and you have requested strict checking.
Host key verification failed.

Get rid of that message :

$ ssh-keygen -f "/home/alamsyah/.ssh/known_hosts" -R 192.168.1.207

/home/alamsyah/.ssh/known_hosts updated.
Original contents retained as /home/alamsyah/.ssh/known_hosts.old
[email protected]:~$ ssh [email protected]
The authenticity of host ‘192.168.1.207 (192.168.1.207)’ can’t be established.
ECDSA key fingerprint is ba:4b:ee:4c:b1:6d:02:41:62:e0:19:1e:c5:11:e7:0b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.1.207’ (ECDSA) to the list of known hosts.
[email protected]’s password:
Last login: Fri Dec 20 20:43:20 2013
OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.

$

Good call.

Lesson learned, I used to use same IP for experiment and this message came out. In future I’ll use different ip for different operating system.

How to update FreeBSD 9.2

Stay Hungry Stay Foolish Sticker
The title a bit strange but I don’t care as I believe on “stay hungry stay foolish” quote :-). My last experience with FreeBSD is FreeBSD 7 and jump to version 9 is make think to relearn all those server stuff I ever knew. I think everything is different know but I prefer to that with experiment way. Document every process that I think interesting. Almost 1 month since I install FreeBSD 9.2 and now I try to update the box. Security update etc.

freebsd-update

I hope this tool still work now.

# freebsd-update fetch
Looking up update.FreeBSD.org mirrors… none found.
Fetching public key from update.FreeBSD.org… failed.
No mirrors remaining, giving up.

Tuning /etc/freebsd-update.conf and change these section :

# BackupKernel yes

# If BackupKernel is enabled, the backup kernel is saved to this
# directory.
# BackupKernelDir /boot/kernel.old

into

BackupKernel yes

# If BackupKernel is enabled, the backup kernel is saved to this
# directory.
BackupKernelDir /boot/kernel.old

save and rerun freebsd-update fetch.

That’s the only thing I care when update or upgrading.

More details available from handbook.

Picture : Stay Hungry Stay Foolish Sticker by Retro_Zombies

in Unix | 185 Words