LeeTibbert

Progress! I believe that I have found the underlying defect on the Unix path. It is not in code I wrote, but I am paying off karmic debt for the...

@armanbilge I have sketched out a PR to fix this issue. I like to create the tests before I do the edits for the fix. Both University & commercial work...

The reason that I suggest this as a good first issue is that the result (confidence in error cases) is useful to the good reputation of Scala Native but not...

Eric, than you for the context. The candles in the darkness (makedocs, section in Contributor's Guide) are far better than the Darkness before. I know, I was there. I created...

Recent discussions about TLS brought me here. I think we all concur that since this involves removing a big chunk, it should be done in a 0.x.0 version change. I...

Yes, asking asking "What would SJS do (a second time)?" is worthwhile. As mentioned above, I think the over-arching issue is getting something (acceptable, we are going to have to...

> Removed in 0.5.0 I concur with the idea/drive/intent but the implementation side of me would substitute 'timely & urgent'. Beyond arriving at design consensus, the major time consuming items...

I mostly concur. > `junk java.security` Two words which, side by each, should cause angina & terror. "Internal usage", "What to do about 0.4.x", and "Finding a home" are Big...

Fun keeps coming: I just discovered `/javax/security/auth/x500/X500Principal.scala` so `javax/security` should be part of the discussion. There is a "cert' subdirectory there also. `X500Principal.scala` has at least one internal user '/java/util/jar/JarEntry.scala'....

To size/scope the `java.security effort`: Everything needs to be looked at by (two or more) sets of eyes before signing off on for 0.4.x (or 0.5.x) These look hard to...