SysLock update

[sYsLoCk]

New update available with important changes:
 
SysLockv4.0c :cool:
 
Please, read the new readme file carefully! :rtfm:

[sYsLoCk]

Hmm... why isn't this thread showing up on the home-page or New Posts? :confused:
 
Edit:
Never mind... it's showing up on the New Posts page now.

[jsixis]

looks like a nice program, if I ever get my Amigas working properly I will check it out
 Thanks

[Thomas]

Without harddrive encryption such a program is not of much use. It only defeats dumb users.

Surely, with Kick 1.3 and bootpri=127 it is rather difficult to access the drive's data but with physical access to the machine and the right skills it can be done quickly.

Either
- connect the harddrive to a Linux machine and use a hex editor to change bootpri or
- connect the harddrive to a Kick 2.0 machine and use the early startup menu to boot from another disk or
- connect a second harddrive to the controller which also has a partition with bootpri=127 but no protection or
- disable the hdd controller and manually mount the partitions loading the driver from floppy disk (especially in the Kick 1.3 era many hdd controllers offered this option for compatibility with kick 1.2).

[sYsLoCk]

looks like a nice program, if I ever get my Amigas working properly I will check it out
Thanks

Thanks for you comment!

[sYsLoCk]

Without harddrive encryption such a program is not of much use. It only defeats dumb users.

That's not a smart remark to make. That's in fact an insult for people who are using this program. It doesn't have to defeat "dumb" users. It's a protection against "dumb" housemates/friends/wife/children. The user is the one that knows the password after all...
 

Surely, with Kick 1.3 and bootpri=127 it is rather difficult to access the drive's data but with physical access to the machine and the right skills it can be done quickly.
 
Either
- connect the harddrive to a Linux machine and use a hex editor to change bootpri or
- connect the harddrive to a Kick 2.0 machine and use the early startup menu to boot from another disk or
- connect a second harddrive to the controller which also has a partition with bootpri=127 but no protection or
- disable the hdd controller and manually mount the partitions loading the driver from floppy disk (especially in the Kick 1.3 era many hdd controllers offered this option for compatibility with kick 1.2).

Yes, I'm fully aware that if you open up your Amiga and change things in there, you'd be able to bypass SysLock and get to the content of the harddrive. Everything is crackable. Even the biggest safe!
But the point is that this program is for Amiga users that want to keep other people away from the contents of their HD. The average housemates/friends/wife/children doesn't have a clue on how to access your HD with SysLock installed. They don't go wrecking your precious Amiga to change/replace HD's or floppy drives.
All I made was a decent system/HD locker for the Amiga community because the AmigaOS lacks a built in one, like PC's have. Compared to other simular (Amiga) lockers, this is the best available:
 
* Disables the CLI-window in the Boot-Menu (so, no access from there).
* Nice GUI interface & fonts.
* Built-in screenblanker.
* Sound samples.
* Installer.
 
If you think you can make a better one, then go ahead. I'm very curious.

[danbeaver]

Syslock,

What is your opinion of PGP's combined hardware (USB dongle) and software encryption of the hardware?

[sYsLoCk]

Syslock,
 
What is your opinion of PGP's combined hardware (USB dongle) and software encryption of the hardware?

I've not (yet) had the time to test one of those PGP projects. It's on my To-Do list.

[AmiDude]

@ Syslock

I've installed your program on  my A1200. I think you did a great job! Well done!
Never mind Thomas, he's just being jealous. He's not capable to develop a program like yours. He makes only worthless commands and stupid useless little WB apps.

[sYsLoCk]

@ AmiDude
 
I see what you mean. Anyway, thanks for using SysLock!

[cgutjahr]

The average housemates/friends/wife/children

Maybe you should state it like that in the readme, because the current description makes it sound like it's the definite answer to all security problems ("protect your harddisk from any unauthorized persons" ... "offers the best protection").

* Disables the CLI-window in the Boot-Menu (so, no access from there).

So it patches Kickstart? That requires one "insecure" boot, so it's basically just eyecandy - everybody who knows how to access the boot menu also knows how to cold start.

[sYsLoCk]

Maybe you should state it like that in the readme, because the current description makes it sound like it's the definite answer to all security problems ("protect your harddisk from any unauthorized persons" ... "offers the best protection").
 
 
So it patches Kickstart? That requires one "insecure" boot, so it's basically just eyecandy - everybody who knows how to access the boot menu also knows how to cold start.

Yes, it offers best potection against average housemates, friends, wife or children. Especially compared to other simular Amiga programs. I clearly stated that last in the read.me file. But I'll change some lines in the read.me file when I upload a future update. Most people don't know anything about AmigaOS; Boot-Menu? They don't have a clue what's that about. And no, it doesn't patches Kickstart. Even with a cold boot, you can't access the CLI window in the Boot-Menu after installing SysLock (except KS2.0). Have you actually tried the program? I'm open to any suggestions.