USB/SD and so on-Mountmanager-Writeprotection with Stikybit

[Blackcrack]

Hy,

i had read on the cia.vc, it is a writing on a Mountmanager..
now my suggestion.. humm, manny peoples had call for lock the data carrier ..
and i did not forget that.. and now, now it is the possible here who can write it direcktly in the Mountmanager of Reactos.. with an Stiki bit, Locked or not locked..
and by side, why not a Cripting-bit with AES or something else on it.. to say,
this carrier iss crypted.

ROSM=Letter/artofpart|writing/nowriting|Crypting/ nocrypting | Cryptingmetode | Cryptedpass

ROSM=C/boot/system|0/1|0/1|AES|%§$%§&$%"%&$§%$%&§$$%"§§%§&%&$%(()=/$%GDFGHG/%&Z

So can Read the Mountmanager wich Metode it is Mounted..
writeprotected, Crypted,pass
Ma by can write this outside of the normal Primary,Extended,Secundary Patitions.. without partitions as a string, direcktly on the harddisk behind the first informations like mbr and so on.. this it is checking the Montmanager too and can work with it..
I think, that's just the right time, to programmin this into... for support
writeprotections and the newest possibilitys of Crypting and Security.
And it is possibility with all mounted Partitins and DataCarriers..
to set writepotections,Crypting and so on.. i think on usb-sticks and so on..
(edit and past 2nd text(more suggestions))
Reactos by self can make a 100MB for booting Partition like W7 and can crypted
the System by self and can call for Pass by Booting if store the (exemple) aes.dll on the 100MB-Partitions and load at the 1.st Stage Boot like Hardwaredrivers and so..
this drivers can store at the 100MB Partition for Boot Reactos..
like bootmgr | /boot/inifiles | /drivers/Sys |/drivers/inf |/drivers/dll
and Change this bootpartition to no-see-partition or get by booting the last drive-letter like Z and the System as own have the C:
Winnt dont need an Swap-partition, make it on the files therefor can Reactos take a "Boot-Partition"(swap)...
the User shold tell wich partition it is the "Boot-Partition" and the "C:\-Partition" for Reactos as Extended Partitioning..
normal partitioning for first Installation can make this automaticly...

(edit and past 3rd text(more suggestions))
and the part of boot can take a mountmanager.dll who look and set the
right partitions automatical and can call the(exemple) aes.dll to call the User
for an Passwort grafikal on bootscreen for decrypting the Systempartition
and get it furter with right passwort to Systempartition to boot
the rest of the SystemPartition,swapfiles and Desktop furter.

the Cryptingsystem mus hold changeable with an dll to use TrueCrypt, blowfish
or other cryptingsystems, newer ones if it is possible... more uncrackable..

Greetings To aNoNyMoUS.... Let be the Human more save him self

best regards
Blacky

[Bblaauw]

Your story is quite hard to follow but hopefully you've made your point.

read-only USB: needs to be done in hardware, not in software. Some USB keys have a switch for it.
encryption: maybe use/integrate TrueCrypt into ReactOS? You'd need to supply a password/key then to open anything beyond FreeLDR.

filesystem protection and user permissions: no chance right now, with FAT as filesystem. NTFS, HFS and some Linux filesystems have more advanced features.

[Z98]

Blackcrack has been warned in the past about his posts. As far as we can tell he uses an auto-translator for English, which we've warned him is unacceptable. It's about the only time we've ever warned anyone about their grammar.

[FlyingIsFun1217]

Surely there is someone on the forums who could translate for him?

FlyingIsFun1217

[Blackcrack]

Hy Z98,

i had a idea/suggestions.. and maby it was helpfully to developing a secure"er" NT-System..
befor i had vorget the idea so i had it wrote down..
this time i dont use an translater and have learn a little bit.. but please,
dont see my wrote in english, see the suggestion behind it,
to make a ... maby secure WinNT ... a possible to get the Users
more save by Hand as microsoft it does..
on look to Cammeralogin and Handprint.. and i dont think,
to have Microsoft not an possible to login into a backdoor in
all windows to use the Pictures and handprints who it is comming
in Win8.. i dont trust Microsoft not realy...
how every.. please Z98, see the suggestions...

bests regards
Blacky

p.s.: if you are realy not understand, so forgett it.....how ever.. sorry..

[vicmarcal]

Hy Z98,

i had a idea/suggestions.. and maby it was helpfully to developing a secure"er" NT-System..
befor i had vorget the idea so i had it wrote down..
this time i dont use an translater and have learn a little bit.. but please,
dont see my wrote in english, see the suggestion behind it,
to make a ... maby secure WinNT ... a possible to get the Users
more save by Hand as microsoft it does..
on look to Cammeralogin and Handprint.. and i dont think,
to have Microsoft not an possible to login into a backdoor in
all windows to use the Pictures and handprints who it is comming
in Win8.. i dont trust Microsoft not realy...
how every.. please Z98, see the suggestions...

bests regards
Blacky

p.s.: if you are realy not understand, so forgett it.....how ever.. sorry..

Hi Blackcrack!
Seems you're progressing with your English.This latest post was more readable than the first one.
If you are using Firefox, just click here: https://addons.mozilla.org/firefox/down ... tn-primary
It will install the English dictionary and it will warn when you are writting incorrectly a word. You'll find yourself improving your English much faster!
Also in the OffTopic Forum Purplegurl is teaching some English rules that can help you a little.

As BBlaauw suggested TrueCrypt seems to be a nice option that fits your needs:

Files can be copied to and from a mounted TrueCrypt volume just like they are copied to/from any normal disk (for example, by simple drag-and-drop operations). Files are automatically being decrypted on the fly (in memory/RAM) while they are being read or copied from an encrypted TrueCrypt volume. Similarly, files that are being written or copied to the TrueCrypt volume are automatically being encrypted on the fly (right before they are written to the disk) in RAM.
Let's suppose that there is an .avi video file stored on a TrueCrypt volume (therefore, the video file is entirely encrypted). The user provides the correct password (and/or keyfile) and mounts (opens) the TrueCrypt volume. When the user double clicks the icon of the video file, the operating system launches the application associated with the file type – typically a media player. The media player then begins loading a small initial portion of the video file from the TrueCrypt-encrypted volume to RAM (memory) in order to play it. While the portion is being loaded, TrueCrypt is automatically decrypting it (in RAM). The decrypted portion of the video (stored in RAM) is then played by the media player. While this portion is being played, the media player begins loading another small portion of the video file from the TrueCrypt-encrypted volume to RAM (memory) and the process repeats. This process is called on-the-fly encryption/decryption and it works for all file types (not only for video files).

More info: http://www.truecrypt.org/docs/?s=version-history
You can crypt the OS partition, the whole HDD, USB sticks, etc...
So you are looking for a ReactOS+TrueCrypt operating system.

[Blackcrack]

hy vicmarcal

humm.. should be installed as default system Feature
directly programming in.. and not as an external encrypting Program
who must work in different Art of NT .. so it is only need the dll
to load as TSR at start of System and work more perfectly..
with less Prozessor load ...
so i think if is see right like it functions ... okey, AES it is
?Hardwarecrypting? then a other encrypting methods ..
but directly build in reactos ...

okey, this is encrypting and decrypting..

no, why i had wrote at first.. the Mountmanager it is in work, like i had read..
there is an possible to implementing this in MountManager per Software
to tell if is the Carrier writeable or not and an Possible to have to
tell which drive letter it should to have, if occupied, then a letter above it.
And this can stored directly by side of patition- informations ma by between partitions-information and Bootrecord .. this was my idea..ehh sorry, suggestions..

p.s. installed

best regards
Blacky

[vicmarcal]

hy vicmarcal

humm.. should be installed as default system Feature
directly programming in.. and not as an external encrypting Program
who must work in different Art of NT .. so it is only need the dll
to load as TSR at start of System and work more perfectly..
with less Prozessor load ...
so i think if is see right like it functions ... okey, AES it is
?Hardwarecrypting? then a other encrypting methods ..
but directly build in reactos ...

Well you know that ReactOS project tries to maintain ReactOS smaller as possible, that way anyone can create, if desired, a special OS as the one you are suggesting: A Crypted OS. Crypting is not by default the Windows XP/2003 behavior, and also not everyone wants a Crypted HDD. They exist :p

no, why i had wrote at first.. the Mountmanager it is in work, like i had read..
there is an possible to implementing this in MountManager per Software
to tell if is the Carrier writeable or not and an Possible to have to
tell which drive letter it should to have, if occupied, then a letter above it.

If I understood you correctly you are suggesting the following:

"You want that when accesing to a Crypted Pendrive, the MountManager warns the user and asks him for the Password to un-crypt it. Giving the opportunity to the user to choose freely the drive letter (D:, F:,G:) where the Pendrive is going to be mounted"
(If I am missing something, please tell me)

Well, Windows lets you to change the letter of any current partition.Just this option is not a default one since the User can get mad(what is this OS asking me?)if we keep asking this question each time he plugs the USB.
MountManager doesn't need to implement the "warning/asking the password" or "forbidding the access to the Crypted HDD/USB stick". TrueType will do this work.
Read all the crypting and secure access features of TrueCrypt. Btw, TrueCrypt should *cough* work *cough* in ReactOS.Maybe not now but in a future.

[Radhad]

Surely there is someone on the forums who could translate for him?

FlyingIsFun1217

He writes the same way in german. That's a big barrier for understanding him because I often don't guess what he thinks about.

[EmuandCo]

Back to topic, I wont allow any grammar bashing again! If you dont wanna answer, then ignore him. Otherwise, answer.

[Radhad]

That's not grammar bashing, it's just complicated to understand him. Nothing more.



I also believe that TrueCrypt is the best effort ReactOS should support for HDD Encryption instead of implementing an own tool for that. It it's not downloadable through RosApps, it should be tested if it's working.

Don't reinvent the squared wheel!

[Blackcrack]

Hy ,

thank you very much EmuandCo

Well you know that ReactOS project tries to maintain ReactOS smaller as possible, that way anyone can create, if desired, a special OS as the one you are suggesting: A Crypted OS. Crypting is not by default the Windows XP/2003 behavior, and also not everyone wants a Crypted HDD. They exist :p

okey.. then let be this by side, the "crypting" Ma by programming anyone it directly inside for Reactos.. like symantec but an private or an Ano... anyone..
The code it is open.. and i see the Problem too.. popularity for now... but later if Reactos finish any anyone can use it.. but this is not the point.. i know..

I also believe that TrueCrypt is the best effort ReactOS should support for HDD Encryption instead of implementing an own tool for that. It it's not downloadable through RosApps, it should be tested if it's working.

jepp, direcktly inside programming as Standartapp for working 100% like mspaint or notepad but this as direct de-encrypting tool. And ma by directly in Mountmanager and dll's as plugin for spezific engryptingand decrypting tool who can be ma by stored on an other Data Carrier as Key-Carrier or possibility use an Password (by booting)...
but this is more showing forward ma by ..

how ever, cryping it is one point... writing and locking it is an other..

"You want that when accesing to a Crypted Pendrive, the MountManager warns the user and asks him for the Password to un-crypt it.

forget the decrypting.. the 2nd thing what i had mean...
was writeable or not writeable.

The Mountmanager can "marked" a hard disk (or an USB-Stick/SD or what ever)
if it is writeable or not writeable , it's mean therewith, for a little bit more
saving the Data Carrier before to be deleted, formatted or something else, should
get an possibility to get an marking on this Data Carrier (writeable or not writeable)..
like Hardware-floppy, an hole or not an hole( the pushing thing, you still shows? )
but this on Software base for all Data carriers directly on the Data carriers between
boot record and partitions-informations. For saving Partitions and Data.. before
deleted or formatted.

Giving the opportunity to the user to choose freely the drive letter (D:, F:,G:) where the Pendrive is going to be mounted"
(If I am missing something, please tell me)

and if it is mounted on F: so take G: and so further ..
Like in Windows NT but Windows marking not the Hardware,
it is writing in the Registry.... but it is the wrong place..
In Linux(Mandriva) have the Data Carrier an ID-Number, no, the Hardware
it is marked with an ID like :
UUID=7898705f-4acc-4780-8172-f8f32e6cee75
this number can handle in the System as a specific Data Carrier.
who can tell which Drive-letter it is become, but the problem it is,
it is know the number in an other Compter ?...
so, why marking the Data Carrier not directly.

writeable, drive letter from Mountmanager marked directly on the Data Carrier.

That requires only a few bits ... on the Data Carrier

best regards
Blacky