rmwebs: The client account passwords are one-way encoded with industry-standard encryption methods. However, we'll probably force new password generation to be 100% safe.
Everyone else: Thanks for being so understanding. I must emphasize that DA installations, updates, your clients' servers, etc. are unaffected by all of this. This is a huge pain for you but it will not trickle down to the functionality of your customer's servers.
Mark
rmwebs: The client account passwords are one-way encoded with industry-standard encryption methods. However, we'll probably force new password generation to be 100% safe.
@Mark
And what about our current software on the servers? - If it has been compromised on your server ........ unless you have a worse compilations of code and configurations than the ones that come with DirectAdmin panel?
@Mark
And what about our current software on the servers? - If it has been compromised on your server ........ unless you have a worse compilations of code and configurations than the ones that come with DirectAdmin panel?
@lemonhead.. would you tell everybody on the internet how you are securing your server / websites / etc.?
you don't understand what I'm asking, do you?
do you understand what your asking here? they just dont know that anwer!
there are several ways to hack into a server, give them some time.
imagin you working in a large office building (60+ levels) and on the floor of the building manager there is no power anymore, there could be several problems
- the powerlines are faulty (hardware)
- the switchboard has a software failure (software)
- somebody switched off power supply (user)
we just dont know that answer yet unless somebody investigates why the power is off *thats what they are doing right now*.... do you automaticly assume that the software of the switchboard or could there be something else wrong?
please wait and let the tech guys find it out!
you don't understand what I'm asking, do you?
this is a non-issue at this moment in time, i'm sure DA are using correct hashing methods (salts, sha etc).
i fully do you want to know if somebody might be able to see your directadmin account password by reversing the encryption method.
this is a non-issue at this moment in time, i'm sure DA are using correct hashing methods (salts, sha etc). Biggest question right now is, how did they hack into the DA server and can this method be repeated to other DA servers
Delivered-To: [email protected]
Received: by 10.229.222.20 with SMTP id ie20cs142998qcb; Wed, 25 May 2011
13:53:25 -0700 (PDT)
Received: by 10.231.140.81 with SMTP id h17mr46297ibu.47.1306356804621; Wed,
25 May 2011 13:53:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from jbmc-software.com (jbmc-software.com [216.194.67.119]) by
mx.google.com with ESMTPS id f2si164940ibe.34.2011.05.25.13.53.24
(version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2011 13:53:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of [email protected]
designates 216.194.67.119 as permitted sender) client-ip=216.194.67.119;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of
[email protected] designates 216.194.67.119 as permitted sender)
[email protected]
Received: from apache by jbmc-software.com with local (Exim 4.76)
(envelope-from <[email protected]>) id 1QPL66-0006f8-Vy for
[email protected]; Wed, 25 May 2011 14:54:30 -0600
To: [email protected]
Subject: DirectAdmin Client Message
From: DirectAdmin <[email protected]>
Message-Id: <[email protected]>
Date: Wed, 25 May 2011 14:54:30 -0600
I doubt it was DA that got hacked, it could've been via PHP for all we know.how did they hack into the DA server and can this method be repeated to other DA servers