Comments for FireDaemon

Comment on Passwordless root SSH Public Key Authentication on CentOS 6 by vjsroamingid

vjsroamingid — Sat, 10 Sep 2011 00:17:28 +0000

Thanks for the bug tip! I never had issue on any other distro but centos 6. Your tip helped me a lot.
The only strange thing is that out of 4 machines it always worked on a particular machine and not on others (prior to fix). CentOS 6 does not look to be stable if such a basic operation has bugs!

Comment on Passwordless root SSH Public Key Authentication on CentOS 6 by H4nd0

H4nd0 — Thu, 18 Aug 2011 02:27:01 +0000

Correct and corrected.

Comment on Passwordless root SSH Public Key Authentication on CentOS 6 by Will

Will — Thu, 18 Aug 2011 02:13:37 +0000

You mean to say create an SSH RSA key, not DSA.

Comment on Passwordless root SSH Public Key Authentication on CentOS 6 by knnniggett

knnniggett — Sat, 13 Aug 2011 21:26:47 +0000

Thanks for the bug tip! That solved my problem. Strange thing is that my selinux came disabled out-of-the-box. Despite that, I still had to apply the mentioned “fix” to get root logins to use an ssh key.

Comment on freeFTPd – free and most secure sFTP Server available by koehler

koehler — Fri, 11 Feb 2011 14:40:28 +0000

If you want FreeFTPd to work as a service, there are a few configurations that you will need to do:
1. In the services section of windows server, select FreeFTPservice. You can have this as automatic, but I set it to manual and ran a script to have it listen on port 22 for my sFTP server and save it as a .cmd file. This script will need to be loaded under the “recovery”/”run program” section. (it will start the program using this script!) (It does not matter when you save the file).
Here is the script:
@echo off
Set log=”C:ftpstartup.log”
echo sleeping 30 seconds > %log%
sleep 30
echo starting service >> %log%
net start freeFTPDService >> %log%
echo looking for listener… >> %log%
for /F “tokens=2″ %%i in (‘netstat -a -n ^| findstr “^.*TCP.*:22.*LISTENING$”‘) do Set FTPPROC=%%i
IF “%FTPPROC%”==”" goto failed
echo Service listening on %FTPPROC% >> %log%
goto end

:failed
echo failed to start service… >> %log%

:end
Set FTPPROC=
Set log=

2. Then you need to have the service run as your USER and not system. This is because if you run it as system, the service will not actually start when you boot up your computer (and if you configure the service, the system will not recognize it).
3. Every time you would like to make a configuration change, you will need to stop the service, make your changes then restart the service. If you do not stop the service, the changes will not be saved.

These are the three things I noticed when setting up my FreeFTP server. It is really easy to set up and it is a Free sFTP server (the only one that is not command line based ) Users can be added in less the 10 seconds, and even with these configurations, only 10 minutes to set up. I recommend it to anyone who would like to try it!

Koehler

Comment on Accessing Session 0 on demand via the command line (Interactive Services Detection) by H4nd0

H4nd0 — Mon, 07 Sep 2009 05:33:08 +0000

1. Console application is unchecked
2. Startup mode is up to you but mine was automatic
3. Show Window is Normal and Interact with Desktop is checked

Comment on Accessing Session 0 on demand via the command line (Interactive Services Detection) by Patrick

Patrick — Sun, 06 Sep 2009 08:59:42 +0000

Hi H4nd0,

thanks for this post.

> How did that happen? Well quite simply, I launched
> C:\Windows\System32\cmd.exe using FireDaemon Pro

I’m running Vista, some questions regarding the above tip:

1. Did you enable the FD option “Console Application”?
2. What is your setting for the FD option “Start-Up Mode”?
3. What are your settings for the FD options “Show Window” and
“Interact with Desktop”?

Kind regards from Germany,
Patrick

Comment on Introducing our Blog by Craig Gunson

Craig Gunson — Mon, 10 Aug 2009 23:35:15 +0000

We recently deployed a service desk system with no support for running as a service. This meant it required constant attention and manual intervention if something locked up or crashed. Fire Daemon has completely solved this issue for us. We now run our service desk 24/7 and never need to manually check the services.