Exporting - the wrong default?

[Stephen Colebourne]

While the JDK cannot afford to compromise on security, many real-world
systems can and do. Software is mostly a trade-off between security,
quality, features, delivery date, design, resources... etc. As such,
this discussion cannot and should not be shut down solely on the basis
of security.

Stephen


On 27 July 2016 at 13:39, dalibor topic <dalibor.topic at oracle.com> wrote:
> On 26.07.2016 18:42, Stephen Colebourne wrote:
>>
>> In many projects
>> packages change names frequently during development, everything is
>> open and locking stuff down is the last thing on peoples minds. While
>> this of course leads to slightly less secure software, it does achieve
>> *business value*.
>
>
> I would recommend Cristina Cifuentes presentation "Are We Ready for Secure
> Languages?" from the recent Curry On conference, of which a recording is
> available at https://www.youtube.com/watch?v=-fC975HLhyc for some less
> anecdotal thoughts on the business value of slightly more secure software.
>
> It even touches briefly on the utility of modules in JDK 9.
>
>
> cheers,
> dalibor topic
> --
> <http://www.oracle.com> Dalibor Topic | Principal Product Manager
> Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
> <tel:+491737185961>
>
> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
>
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
>
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>
> <http://www.oracle.com/commitment> Oracle is committed to developing
> practices and products that help protect the environment