From owner-freebsd-hackers Wed Oct 13 7:58:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 2D5C014E25 for ; Wed, 13 Oct 1999 07:57:45 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id QAA49394; Wed, 13 Oct 1999 16:55:18 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <38049D55.FF4E2812@oskar.nanoteq.co.za> Date: Wed, 13 Oct 1999 16:55:17 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton , freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? References: <199910131430.AAA53879@gizmo.internode.com.au> Content-Type: multipart/mixed; boundary="------------4AF8CDD17664E320C38956C7" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------4AF8CDD17664E320C38956C7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Your close. I actually made a bootable CD which installs a modified version of FreeBSD, with our product running on on top of it. The CD automatically boots up, installs everything, configures everything and then it asks you for a password. At this stage it gathered information of the particular system. It uses this information and a private key to encrypt the root password and then generates a signiture. The customer phones / mail us with this signiture, we decrypt it using our public key. Now we generate the required key which they have to enter for the installation to complete. In this signiture we got from them we have the followinf info : --> Motherboard used --> Bios Revision --> Root password --> admin password --> other info like disk sizes etc. Only we have the root password, they can change the admin password, and you have to log in as admin first before you can login as root. So, we can do support on the product, since we have the root password, if they give us access via admin password. No problem, the product has been working something like this for 11 years. Now, the machine won't be able to boot if they had'nt entered the correct code which we mail to them, since the kernel is encrypted with it etc etc. So can you pleasssseee now tel me how to get this info ? --> Motherboard used --> Bios Revision Greetings --------------4AF8CDD17664E320C38956C7 Content-Type: text/x-vcard; charset=us-ascii; name="jkruger.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Johan Kruger Content-Disposition: attachment; filename="jkruger.vcf" begin:vcard n:Kruger;Johan tel;cell:+27 83 3015923 tel;fax:+27 12 6651343 tel;home:+27 83 3015923 tel;work:+27 12 6651338 x-mozilla-html:FALSE org:Nanoteq;Development version:2.1 email;internet:jkruger@oskar.nanoteq.co.za title:Mr adr;quoted-printable:;;P.O BOX 12872=0D=0AOnderstepoort=0D=0A0110=0D=0ASouth Africa;Pretoria;Gauteng;0110;South Africa x-mozilla-cpt:;0 fn:Johan Kruger end:vcard --------------4AF8CDD17664E320C38956C7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message