From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.66.138.79 with SMTP id qo15mr7084312pab.34.1386503612012; Sun, 08 Dec 2013 03:53:32 -0800 (PST) X-Received: by 10.182.96.135 with SMTP id ds7mr101149obb.1.1386503611832; Sun, 08 Dec 2013 03:53:31 -0800 (PST) Path: border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.snarked.org!newsfeed.news.ucla.edu!usenet.stanford.edu!i10no4073905pba.1!news-out.google.com!9ni3048qaf.0!nntp.google.com!p15no12460321qaj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 8 Dec 2013 03:53:31 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=109.148.248.100; posting-account=pmkN8QoAAAAtIhXRUfydb0SCISnwaeyg NNTP-Posting-Host: 109.148.248.100 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <9f50bb3f-c2f2-4b15-bc18-dc5b397493c1@googlegroups.com> Subject: Encrypt your Archived Sourcecode. From: Austin Obyrne Injection-Date: Sun, 08 Dec 2013 11:53:31 +0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 3623 Xref: number.nntp.dca.giganews.com comp.lang.ada:184139 Date: 2013-12-08T03:53:31-08:00 List-Id: The reasons why you should do this are increasing day by day. The latest o= ne is malware called =93CryptLocker=94. This gets into your computer after= they have conned you into opening an email or PDF attachment =96 it then e= ncrypts all your important data including your important sourcecode. The n= ext step is to hold you to ransom until you pay a =91bitcoin=92 fee to have= them unlock it again for your use. This malware is easily enough prevented by downloading free =93CryptPrevent= =94 but damaging beyond belief to the unwary if no precautions are taken. B= ut there are others and there will always by threats to your security of in= formation and worse still embedded systems. Encrypting Sourcecode Practise Demo. Open a large file of say 1500 lines of source code (any size of file will d= o but we are demonstrating scope here also). Highlight all =3D> Copy =91 n= paste everything into the AdaGIDE editor =3D> save this as a file (.dat or= .txt) into the common folder and call it =91CodeFilePlaintext.dat=92 say. Open your =93SureCrypt=94 encryption software and encrypt the saved file. Encryption. When prompted call, =91CodeFilePlaintext.dat=92 When prompted again, Name the encrypted file, =91CodeFileCipherText.dat=92(say) Save this file to your hard drive and store an off-line backup copy. Decryption. When prompted call, =91CodeFileCipherText.dat=92 Name the decrypted file, =91CodeFileMessageText.dat Returning to normal work, Open =91CodeFileMessageText.dat in the AdaGide editor =96 Build, Run as us= ual. *No need to labour the importance of program source code as a target for an= y and all malware. If =91CryptoLocker=92 tries to hold you to ransom just tell =91em to keep i= t, you have a back up and they cannot decrypt what they are holding as =93s= uperencrypted=94 data now that is worthless to them or to anybody else eith= er. The salient thing to note here for programmers is the ease of encryption an= d decryption of the source code which is always done by a few mouse clicks = without leaving the development environment =96 programmers should adopt th= is practice as de rigeuer safe backup practice in my view.- only takes abou= t 30 seconds extra in time and a few mouse clicks. This is a well-meant intrusion on your comp.lang.ada site. Bear with it please. adacrypt