Category: News

Support for execute-only (xonly) code
(on which we
reported earlier)
has been committed to -current by Theo de Raadt (deraadt@).

The commits
were:

Read more…

The true king rules the game.

https://www.dailymotion.com/library/playlist/x7pjsr

watch it on web browser like chrome or firefox to activated the subtitle.
if u watch it on phone or iphone app it cannot show the subtitle.

“가보니 곰팡이 필 것 같은 반지하방”

“나는 수퍼리치다”

월드스타 팝페라 테너 임형주.

부유한 가정에서 걱정 한 번 없이 자랐을 것 같은 그가 짠내나는 유학기를 털어 놓습니다.

도착하자마자 부푼 기대를 안고 찾아 간 집은 한마디로 ‘뉴욕판 기생충’의 촬영지였습니다.

큼직한 단독주택에서, 임형주 그가 머물 곳은 주택 지하에 위치한 고작 작은 창문 하나 달려 있는 방이었습니다.

햇볕이 들어오길 기대하는 건 사치였고 눈에 보이진 않지만 곰팡이 냄새 같은 쾌쾌한 향은 사라지지 않았습니다.

하지만 IMF 직후 전세계 사람들이 힘들게 살아가던 시절, 임형주는 혼자 이 난항을 이겨내고 싶었습니다.

“당시 20년 전인데 환율이 1600원, 1800원으로 치솟아 있었어요. 철이 일찍 들었는지 부모님께 손을 크게 벌리고 싶지 않더라고요.”

그가 버틸 수 있는 이유는 단 하나 줄리어드음대 예비학교 프리컬리지 프랩 스쿨 합격!

“그 생각 그 일념 하나였기 때문에 진짜 1%도 고생인지 모르고 재밌었어요.”

그는 힘든 상황을 영화의 주인공이 된 마냥 자신을 소공녀라고 상상하며 살아 갈 힘을 만들었습니다.

끈기와 정신력으로 결국 성악과 심사위원 만장일치로 줄리어드음대 예비학교 성악과에 합격합니다.

“당시 제 생색이 추헤해서 장학금을 준다고 한 것 같아요”라고 농담 삼아 털어 놓은 임형주.

어린 나이에도 자존심 하나도 버틴 그는 “나는 수퍼리치다. 장학금을 안 받겠다”라며 거절합니다.

어린 마음에 한국을 무시한다는 생각이 들어 나온 용기였습니다.

Hello, interested in what you have been up to in the latest 10+ years in rubyland / gemverse? To (auto-)generate timelines for personal profiles or for “curated” collections I have started to put together a new gem, that is, gemverse, for easy (re)use. The gemverse incl. rubygems API V1 wrapper lite; gem version cache, gem timeline reports, ‘n’ more. For some first real-world sample pages see the gem timeline of Thomas Leitner, Gerald Bauer, Victor Shepelev or the Ruby Code Commons (COCOS) Collection. It’s still the early days. Questions, comments & suggestions more than welcome. Cheers. Prost.

A common criticism directed at F-Droid is that F-Droid signs published APKs
with its own keys. Using our own keys doesn’t mean insecure — we have a good
track record (and keep the keys on a dedicated, air-gapped, offline
machine) whilst
others may not — but this does mean that our users need to trust a third
party other than the upstream developers.

Having a different signature can also inconvenience users by making it
impossible to install updates from other channels; this can be especially
inconvenient when we have difficulty providing an update for an
app. Developers also sometimes need to tweak their setup for F-Droid,
e.g. disabling an in-app updater or adding the F-Droid signature for
verification.

F-Droid is not the only app store publishing APKs signed with its own key —
Google Play does the same now. With “code transparency for app
bundles”,
Google provides a means to verify that the DEX files and native libraries in
an APK are identical to those the developer provided. This does address some
of these concerns, but code transparency does not protect many other
important files in the APK, like interpreted code or assets. And unlike APK
signatures, it is entirely optional (and an extra burden for developers) and
verification must be performed manually. It also does not solve the
inconvenience of being unable to install an APK with a different signature.

F-Droid has had a better solution for these problems for quite a
while:
reproducible
builds. However, it was
never widely used. One of the reasons is that it sounds difficult to
achieve. We had few reproducible apps (to be precise: only 6) and some of
them suffered from problems because of the use of reproducible
builds. Basically, we didn’t bother to mention reproducible builds unless
the upstream developers showed an interest. As a result, many developers
never even heard of reproducible builds, let alone that F-Droid supports
them, or attempted to use them for their own apps.

In response to some of those criticisms, we started encouraging new apps to
enable reproducible
builds. It turns out
that reproducible builds are not so difficult to achieve for many apps. In
the past few months we’ve gotten many more reproducible apps in F-Droid than
before. Currently we
can’t highlight which apps are reproducible in the client, so maybe you
haven’t noticed that there are many new apps signed with upstream
developers’ keys. If you have some third-party repositories enabled,
e.g. the IzzySoft one, you may find that sometimes you can update the app
from the main repository even if you installed it from another one.

Meanwhile, now that we’ve encountered many more test cases than before, we
also found many
new
problems
that affect reproducibility. Fortunately we also found workarounds for most
of them and developed some tools to make APKs
reproducible, mainly
thanks to @obfusk’s contributions. There are still some open issues and we
are still working hard to solve them. If you are interested in reproducible
builds, contributions are always welcome.

Has anyone ever heard of the Apple YACC, or YACCintosh? it was a 68010 prototype mac intended to do colour in 1986. Weirdly enough someone managed to find the ROMs *and* the PALS for it, but no schematics have turned up yet. All of the stuff is on bitsavers. I do not know what to add here. This seems to be one of the most obscure – if not the most obscure – Apple efforts out there, as there are virtually zero references of it online.