- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev
by Sven Van Caekenberghe June 1, 2020

June 1, 2020

> On 1 Jun 2020, at 06:39, Jerry Kott <jkott(a)image-ware.com> wrote: > > If you read the text of the EAR and take into account all other facts, I think that the notion that anyone should get into trouble by copying open source Smalltalk crypto libraries to other repositories is just a pure FUD. This software is open source, it is publicly available including the source code, it is hosted on a domain that is controlled by a non-US entity, and itâs easily accessible in its current form from countries that are currently on the US âvorbotenâ list. Indeed.

2 1

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev
by Richard Sargent May 31, 2020

May 31, 2020

Thanks, Bruce. The part about (the possibility that) squeak source is configured to restrict distribution was the missing piece for me. I had previously assumed (hah!) that it would be available to anyone anywhere. On Sun, May 31, 2020, 10:39 Bruce O'Neel <bruce.oneel(a)pckswarms.ch> wrote: > > Hi, > > So addressing only the crypto software issue and with the caveat that I am > also not a lawyer but I have had to deal with certain aspects of this in > the past.... > > Crypto software is one of those bizarre dual use items in terms of arms > imports and exports. While we as geeks just think of this is software or > mathematics and might be confused as to why governments care, governments > do care deeply about this. And their way of expressing how much they care > about this issue is by passing laws and prosecuting folks. > > One of the easiest ways to get in trouble is for one to make the software > available to residents and/or citizens of certain countries as well as > available to people on a long list kept by different governments. We can > have a long debate about the morality of this concept but those who make > the laws have decided that is the law. And often these laws are crafted > such that the executive can change important details on short notice and > that puts the risk of prosecution at the whims of different world leaders. > > The license that the software is released under is not important. > > What Ron is stating is that squeak source supplied some additional > protections to prevent accidentally making the software available to folks > who the US feels should not have access. > > If you have moved the software to another hosting provider without the > permission or knowledge of the author, and therefore the owner of the > software, you have put that person at additional risk. In addition you and > the hosting provider are taking on additional risk. > > If it was moved to GitHub I strongly recommend reviewing their policies on > trade controls and what risks you assume. > > https://help.github.com/en/github/site-policy/github-and-trade-controls > > > Finally I would strongly recommend talking to a competent legal advisor > who is deeply familiar with the details of these laws. They are complex > and highly variable between different parts of the world. > > I know this seems like a lot of trouble and wasted time but you can spend > a giant amount of time and money defending oneself from arms trafficking > charges. > > cheers > > bruce > > *30 May 2020 14:43 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > <stephane.ducasse(a)inria.fr>> wrote:* > > Hi all > > This is the week-end and we worked super well yesterday during the sprint. > Lot of good enhancements - Thanks a lot to all the participants. > I not really happy to be forced to do it on a sunny saturday but Iâm doing > it to clarify points. > > Esteban sent me this text that was posted on Squeak-Dev (I personally do > not read squeak related forums because > I have not the time and my focus is Pharo, its consortium, my team, my > research and my family). > > We have to react because > - We do not really at ***all** understand this email > - We did not kicked anybody from our mailing-list from ages - so ron is > lying. In the past we even had discussion with ron - so we do not > really understand. May be we got problem to log on our mailing-lists. > We have no idea because we are working and not looking at such things. > - When we migrated smalltalkhub to readonly we payed attention to make > sure that private projects stay private. > We did not migrated smalltalkhub for fun. We MUST do it or it will be done > by our infrastructure! > - Now the cryptography packages are MIT and they are public anyway. So > again we do not understand anything. > > We do not get why Ron contacted us because we announced the migration > publicly way in advance and we will keep > the Smalltalkhub frozen repo for at least next 5 years. > > I feel really sorry to hear such kind of email because we do not want to > fight with anybody. > Our goal is to make sure that people can work with Pharo and expand their > business and knowledge. > We are working hard to make sure that people can invent their future with > Pharo and people that know us personally > know that we are not lying. > > S > > > > Hi all, > > I've tried to work with the Pharo group but they keep kicking me out of > their mailing list. I've already mentioned this a number of times to the > Pharo group but nobody seems to care. > > BOLD BOLD BOLD PLEASE TAKE THIS SERIOUSLY BOLD BOLD BOLD > > I am not a lawyer but we used very good lawyers to make the squeaksource > repository a safe place to do cryptography work. If you are working on > cryptography DO NOT POST your code anywhere except squeaksource. > Especially if you are in the USA. The ONLY repository that is approved to > host our cryptography code in the USA and therefore not subject to criminal > violations is squeaksource. It is a CRIME in the USA to move code and make > it available on the internet for everyone to download! It must be hosted > on squeaksoruce.com or another location that is also properly registered. > > IF YOU COPIED CRYPTOGRAPHY CODE TO ANOTHER REPOSITORY THAT IS NOT > REGISTERED I would recommend you delete it immediately. > > END BOLD! > > Please feel free to post this to the Pharo mailing list because they > apparently do not want to hear from me! > > All the best, > > Ron Teitelbaum > > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > >

1 0

[Pharo 9.0] Build #323: 6378-SmallInteger-methods-are-calling-for-test-and-executable-comment
by ci-pharo-ci-jenkins2＠inria.fr May 31, 2020

May 31, 2020

There is a new Pharo build available! The status of the build #323 was: FAILURE. The Pull Request #6465 was integrated: "6378-SmallInteger-methods-are-calling-for-test-and-executable-comment" Pull request url: https://github.com/pharo-project/pharo/pull/6465 Issue Url: https://github.com/pharo-project/pharo/issues/6378 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #322: 6320-RBExtraBlockRule-does-not-check-for-cull--co
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #322 was: FAILURE. The Pull Request #6416 was integrated: "6320-RBExtraBlockRule-does-not-check-for-cull--co" Pull request url: https://github.com/pharo-project/pharo/pull/6416 Issue Url: https://github.com/pharo-project/pharo/issues/6320 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #321: extract-return-from-conditionals-for-packages-s
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #321 was: SUCCESS. The Pull Request #6437 was integrated: "extract-return-from-conditionals-for-packages-s" Pull request url: https://github.com/pharo-project/pharo/pull/6437 Issue Url: https://github.com/pharo-project/pharo/issues/extract Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #320: Fix https://github.com/pharo-vcs/iceberg/issues/1359
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #320 was: SUCCESS. The Pull Request #6454 was integrated: "Fix https://github.com/pharo-vcs/iceberg/issues/1359" Pull request url: https://github.com/pharo-project/pharo/pull/6454 Issue Url: https://github.com/pharo-project/pharo/issues/fix/iceberg/1359 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #319: 6247-asPrimitive-deverses-a-comment-and-some-inline-comment-too
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #319 was: FAILURE. The Pull Request #6450 was integrated: "6247-asPrimitive-deverses-a-comment-and-some-inline-comment-too" Pull request url: https://github.com/pharo-project/pharo/pull/6450 Issue Url: https://github.com/pharo-project/pharo/issues/6247 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1137: 6256-MacRomanUnicode-char-converter-methods-are-backwards
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #1137 was: SUCCESS. The Pull Request #6365 was integrated: "6256-MacRomanUnicode-char-converter-methods-are-backwards" Pull request url: https://github.com/pharo-project/pharo/pull/6365 Issue Url: https://github.com/pharo-project/pharo/issues/6256 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #318: extract-return-from-conditionals-for-packages-n
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #318 was: SUCCESS. The Pull Request #6433 was integrated: "extract-return-from-conditionals-for-packages-n" Pull request url: https://github.com/pharo-project/pharo/pull/6433 Issue Url: https://github.com/pharo-project/pharo/issues/extract Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #317: 6277-RBTemporaryNode-does-not-return-the-right-info-when-in-a-sequence-node
by ci-pharo-ci-jenkins2＠inria.fr May 29, 2020

May 29, 2020

There is a new Pharo build available! The status of the build #317 was: SUCCESS. The Pull Request #6417 was integrated: "6277-RBTemporaryNode-does-not-return-the-right-info-when-in-a-sequence-node" Pull request url: https://github.com/pharo-project/pharo/pull/6417 Issue Url: https://github.com/pharo-project/pharo/issues/6277 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0