Hi,
Who is the official maintainers of OnGuard located in the Lazarus CCR
repository?
The wiki page doesn't give much information about who maintains it, what is
(not) working etc.
http://wiki.freepascal.org/OnGuard
I want to use the OnGuard components with a non-GUI projects and non-LCL
In our previous episode, Graeme Geldenhuys said:
A quick question to anybody that previously worked on OnGuard:
* What is the IBO_CONSOLE defines for? What is IBO?
http://www.ibobjects.com/
--
___
Lazarus mailing list
Marco van de Voort wrote:
* What is the IBO_CONSOLE defines for? What is IBO?
http://www.ibobjects.com/
Thanks Marco. Still makes no sense why there is a special DEFINE for that?
If you want Console support, split the units into GUI and non-GUI packages.
For security features (core code)
Graeme Geldenhuys schreef:
Hi,
Who is the official maintainers of OnGuard located in the Lazarus CCR
repository?
Bogusław Brandys did this port.
See also his recent mail to this list:
http://lists.lazarus.freepascal.org/pipermail/lazarus/2010-February/049310.html
Vincent
--
On Tue, 9 Feb 2010 23:05:31 +0200
Juha Manninen juha.manni...@phnet.fi wrote:
[...]
The ideprocs version is a simple alias. I will delete it.
The codetools and lcl are separate and independent things (by license
and by directory).
The ideprocs version is an alias to function in
Vincent Snijders wrote:
Graeme Geldenhuys schreef:
Hi,
Who is the official maintainers of OnGuard located in the Lazarus CCR
repository?
Bogusław Brandys did this port.
See also his recent mail to this list:
http://lists.lazarus.freepascal.org/pipermail/lazarus/2010-February/049310.html
I dug into the code a little bit and here's what seems to be the problem:
In TLazBuildApplication.BuildProject after the
Project1:=LoadProject(AFilename); the TargetCPU is correct:
(gdb) print PROJECT1^.FCOMPILEROPTIONS^.FTARGETCPU
$51 = 0x77fe7e10 'i386'
However, a few lines after that, it
Bogusław Brandys wrote:
Yep.I did the port.Currently I have no time to actively maintain it.It
worked some time ago and I added some new code to read HDD hardware
serial number but as I not needed this components I have no strong
motivation to continue the efforts.
How well did you test
Graeme Geldenhuys escreveu:
Query the date/time value of the '/bin' directory under Linux, or
'C:\Windows' or 'C:\WinNT' under Windows. Then work out how many seconds or
milliseconds since say 1980-01-01. You then have a pretty unique value. The
chances of somebody else running your software and
On 10 February 2010 18:12, Luiz Americo Pereira Camara
luiz...@oi.com.br wrote:
In the other side, knowing that a cracker can change the time stamp of that
folder to match other system
Make no mistake, there is no single fix to ensure a product is 100%
secure. This is especially true if the
On 10 February 2010 17:12, Graeme Geldenhuys graemeg.li...@gmail.com wrote:
How well did you test the reading of HDD serial number?
I think I found another alternative to find the HDD serial number.
Getting the boot define is fairly easy, so is the serial number for a
ATA (IDE) hard disk. As I
Option 1)
UUID look-up can be done via /var/log/udev
This same file also gives you ALL the information about each device,
including the long and short serial number.
No such file in OpenSuse 11.2.
Option 2)
Knowing the UUID or device (eg: /dev/sda1) one can simply do a lookup
in the
Graeme:
Query the date/time value of the '/bin' directory under Linux, or
'C:\Windows' or 'C:\WinNT' under Windows. Then work out how many seconds or
milliseconds since say 1980-01-01. You then have a pretty unique value. The
chances of somebody else running your software and having installed
Matt Shaffer wrote:
Is it really accurate to the millisecond?
As far as Windows and MSDN documentation, the answer seems to be yes. The
resolution of create time is 10 milliseconds.
http://msdn.microsoft.com/en-us/library/ms724290(VS.85).aspx
Anyway, also interested if
OEMs like HP would
Juha Manninen wrote:
Option 1)
UUID look-up can be done via /var/log/udev
No such file in OpenSuse 11.2.
I thought it would be to easy. :-)
/dev/disk/by-id/ has some files :
/dev/disk/by-id/ata-Maxtor_6B200P0_B419N81H
Excellent, so your hard drive serial number is B419N81H. Two
El 11/02/2010 8:15, Graeme Geldenhuys escribió:
UUID look-up can be done via /var/log/udev
No such file on Debian testing.
But /dev/disk/by-id/ has the files, has many files!
ata-ASUS-PHISON_SSD_SOQ2882217
ata-ASUS-PHISON_SSD_SOQ2882217-part1
ata-ASUS-PHISON_SSD_SOQ2882259
16 matches
Mail list logo
