The module will support Cryptoworks cards. It isn't complete because the RSA part for box key handling is missing.
The local Cryptoworks card init is based on open source oscam.

Example by ORF card:

	Info: Server    [20:37:00.268] Loading sc_cw.mdl ...
	Info: Module    [20:37:00.273] sc_cw: Start Cryptoworks card reader
	Info: Module    [20:37:00.273] sc_cw: Resetting card...
	Info: Module    [20:37:01.038] sc_cw: ATR: 3B78120000A0C403008FF19000
	Info: Module    [20:37:01.038] sc_cw: CryptoWorks card detected
	Info: Module    [20:37:02.007] sc_cw: CryptoWorks, CAID 0D05, ASCII Serial: 85xxxxxxxxx, Hex Serial: 02000xxxxx
	Info: Module    [20:37:02.633] sc_cw: CryptoWorks, Issuer ORF, Id: 08, Bios: 03, Pin: unknown, mfid: 3F02
	Info: Module    [20:37:02.633] sc_cw: CryptoWorks, Providers: 04, 08, 0C, 10
	Info: Module    [20:37:02.900] sc_cw: CryptoWorks, Provider 0, ID: 04, Name: ORF
	Info: Module    [20:37:03.296] sc_cw: CryptoWorks, CHID 0010, Date: 2009/03/17 - 2009/04/15, Name: ATV+
	Info: Module    [20:37:03.396] sc_cw: CryptoWorks, CHID 0001, Date: 2009/03/17 - 2009/04/15, Name: ORF All
	Info: Module    [20:37:03.487] sc_cw: CryptoWorks, CHID 0001, Date: 2010/09/06 - 2011/04/04, Name: ORF All
	Info: Module    [20:37:03.584] sc_cw: CryptoWorks, CHID 0010, Date: 2010/08/25 - 2011/03/26, Name: ATV+
	Info: Module    [20:37:03.912] sc_cw: CryptoWorks, Provider 1, ID: 08, Name: Sector 2
	Info: Module    [20:37:04.483] sc_cw: CryptoWorks, Provider 2, ID: 0C, Name: Sector 3
	Info: Module    [20:37:05.075] sc_cw: CryptoWorks, Provider 3, ID: 10, Name: Sector 4
	Info: Module    [20:37:05.447] sc_cw: CryptoWorks, CHID 0043, Date: 2010/12/10 - 2011/02/23, Name: 003
	Info: Module    [20:37:05.547] sc_cw: CryptoWorks, CHID 0042, Date: 2010/12/10 - 2011/02/23, Name: 002
	Info: Module    [20:37:05.647] sc_cw: CryptoWorks, CHID 0044, Date: 2010/12/10 - 2011/02/23, Name: 004
	Info: Module    [20:37:05.747] sc_cw: CryptoWorks, CHID 0048, Date: 2010/12/10 - 2011/02/23, Name: 008
	Info: Server    [20:37:05.809] Added Card info of sc_cw to card list
	Info: Server    [20:37:05.809] Loaded module: sc_cw.mdl, Version: V 1.0, Author: Project:Keynation

How is it working:
Each card module have its unique INI file.
Example: sc_cw.mdl -> sc_cw.ini
In this INI file there have to be a section named like the file name:
Example: sc_cw.ini -> [sc_cw]
If this match you can set COM port, baudrate,....

Example for 2 local Cryptoworks cards
First local card is connected to COM1
Second local card is connected to COM3

Just make a copy of the module and rename like you want:
First: sc_cw_1.mdl -> sc_cw_1.ini -> [sc_cw_1] -> Port=COM1
Second: sc_cw_2.mdl -> sc_cw_2.ini -> [sc_cw_2] -> Port=COM3


It is also possible to use this module with original vPlug by vahid (tested with 2.6.4).
BUT vPlug only checks the first module if the CAID match. So you have to remove/rename the "cryptoworks.mdl"

vPlug_Server 1.0.2.11 will check now all modules if CAID match. So if the channel can not be decrypted by EMU it will check if any other module for this CAID exists.
You can set priority which module will checked first by the filename of the module.
