<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Just in time for xmas,<div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Second byte of T.O.L.A. via another P.J.C.I.S. @ <a href="https://www.aph.gov.au/Parliamentary_Business/Committees/Joint/Intelligence_and_Security/ReviewofTOLAAct" class="">https://www.aph.gov.au/Parliamentary_Business/Committees/Joint/Intelligence_and_Security/ReviewofTOLAAct</a></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 15 Dec 2018, at 11:19, <a href="mailto:openssl@foocrypt.net" class="">openssl@foocrypt.net</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Rather than going down the political or policy line, perhaps it may be prudent to discuss the technical solutions to testing the engine, regardless of the OS it is running on.<br class=""><br class="">How does one validate and test the engines during / after compile to ensure their ‘trust’ ?<br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On 15 Dec 2018, at 10:42, Viktor Dukhovni <<a href="mailto:openssl-users@dukhovni.org" class="">openssl-users@dukhovni.org</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">On Dec 14, 2018, at 5:42 PM, <a href="mailto:bmeeker51@buckeye-express.com" class="">bmeeker51@buckeye-express.com</a> wrote:<br class=""><br class="">I simply wanted a clear statement so I can make an informed decision whether or not I should use OpenSSL in future projects. I now have my answer. Thank you.<br class=""></blockquote><br class="">This is not the right forum for that question. The bill is too<br class="">new for a policy response to have been considered or agreed.<br class=""><br class="">OpenSSL has committers from many countries. OpenSSH also<br class="">has an Australian maintainer, have they published a policy?<br class=""><br class="">I am sure there are Australian contributors to Linux, NetBSD,<br class="">FreeBSD, OpenBSD, Android, ...<br class=""><br class="">Avoiding all taint from anything touched by Australia will not<br class="">be easy.<br class=""><br class="">-- <br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Viktor.<br class=""><br class="">-- <br class="">openssl-users mailing list<br class="">To unsubscribe: <a href="https://mta.openssl.org/mailman/listinfo/openssl-users" class="">https://mta.openssl.org/mailman/listinfo/openssl-users</a><br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></div></div><br class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">—<br class=""><br class="">Regards,<br class=""><br class="">Mark A. Lane<br class=""><br class=""><br class="">Be Protected, Get ….…..<br class=""><br class="">The FooKey METHOD :<br class=""><br class=""><a href="http://foocrypt.net/the-fookey-method" class="">http://foocrypt.net/the-fookey-method</a><br class=""><br class=""><br class="">The common flaws in ALL encryption technologies to date are :<br class=""><br class=""><br class="">1. Typing on a KeyBoard to enter the password<br class="">2. Clicking on the Mouse / Pointer device that controls the location of the cursor<br class="">3. Some person or device looking / recording your screen as you type the password<br class="">4. The human developing a password that is easily guess, or can be brute forced due to its length<br class="">5. Sharing the password with a third party to decrypt the data<br class="">6. Storing the encrypted data in a secure location so no unauthorised access can be made to either the key(s) to decrypt the data or the encrypted data itself<br class="">7. The Right Wing Policies of the Liberal Party of Australia, being forced into law so they can all make it to the xmas party…!<br class=""><br class=""><br class="">FooCrypt, A Tale Of Cynical Cyclical Encryption, takes away the above ‘BAD GUYS’ by providing you with software engineered to alleviate all the above.<br class=""><br class=""><br class=""><br class="">© Mark A. Lane 1980 - 2017, All Rights Reserved.<br class="">© FooCrypt 1980 - 2017, All Rights Reserved.<br class="">© FooCrypt, A Tale of Cynical Cyclical Encryption. 1980 - 2017, All Rights Reserved.<br class="">© Cryptopocalypse 1980 - 2017, All Rights Reserved.<br class=""><br class=""></div>
</div>
<br class=""></body></html>