July 29, 2010
東京の111歳男性、実は30年前に死亡していた ミイラ化で発見(産経新聞) - livedoor ニュース

 その後、53歳の孫が千住署を訪れ、「祖父は『ミイラになりたい』『即身成仏したい』と言って30年前に自室に閉じこもったままだ」と説明。直後に同署員が自宅でミイラ化した男性の遺体を発見した。

Posted via email from hdknr’s posterous | Comment »

データの上で生き続ける親 - ふじながたかみの日本御臨終宣言

死んだ親の年金で食っている連中がいる。しかもプライバシー保護の名目で覆い隠され、死亡届も出ていないから生きているか死んでいるかさえわからない…。要するにこの予言は「近い将来、下の世代を養うための150歳以上の高齢者住民基本台帳上で続出する」という予言だった。いや、近い将来でなくてもリアルタイム日本のどこかでそれが行われていて摘発も受けているという話だから、予言どころの話ではなく現実にありうる(150歳というのを別にすれば現在進行形レベルの話である。恐ろしい。何が長寿大国だ、産経新聞。今後一切、住民基本台帳上のデータは当てにするな。

国民に番号を配ると解決できますか?

Posted via email from TECHNOHIDELIC | Comment »

2:13pm  |   URL: http://hdknr.com/post/873843479
FILED UNDER: identity 
Bookmark and Share
July 9, 2010
国民IDのシステム開発に6100億円 - 日経コンピュータReport:ITpro

今回、内閣官房の「社会保障・税に関わる番号制度に関する検討会」が試算した 6100億円は、この制度を実現するための開発費のみだ。運用費や周辺ビジネスを合わせると、IT業界にとっては大きなビジネスが期待できる。

Posted via email from hdknr’s posterous | Comment »

June 9, 2010
Amazon.com: Cloud Security and Privacy: An Enterprise Perspective on Risks and…

Amazon.co.jp: クラウド セキュリティ&プライバシー ―リスクとコンプライアンスに対する企業の視点: Tim Mather, Subra Kumaraswamy, Shahed Latif, 下道 高志(監訳), 笹井 崇司: 本

May 19, 2010
When to Use Identity Delegation

What is identity delegation?

Identity delegation is a feature of Active Directory Federation Services (AD FS) 2.0 that allows administrator-specified accounts to impersonate users. The account that impersonates the user is called the delegate. This delegation capability is critical for many distributed applications for which there is a series of access control checks that must be made sequentially for each application, database, or service that is in the authorization chain for the originating request. Many real-world scenarios exist in which a Web application “front end” must retrieve data from a more secure “back end”, such as a Web service that is connected to a Microsoft SQL Server database.

For example, an existing parts-ordering Web site can be enhanced programmatically so that it allows partner organizations to view their own purchase history and account status. For security reasons, all partner financial data is stored in a secure database on a dedicated Structured Query Language (SQL) server. In this situation, the code in the front-end application knows nothing about the partner organization’s financial data. Therefore, it must retrieve that data from another computer elsewhere on the network that hosts (in this case) the Web service for the parts database (the back end).

For this data-retrieval process to succeed, some succession of authorization “hand-shaking” must take place between the Web application and the Web service for the parts database, as shown in the following illustration.

02811fcd-fdf1-40fb-adf7-741097ac956c

Because the original request was made to the Web server itself, which is likely to be located in a completely different organization from the organization of the user who is attempting to access the Web server, the security token that is sent along with the request does not meet the authorization criteria required to access any other computer besides the Web server. Therefore, the only way that the originating user request can be fulfilled is by placing an intermediate federation server in the resource partner organization to help with reissuing a security token that does have the appropriate access privileges.

Posted via web from 原宿工業大学 | Comment »

April 28, 2010
Agentinquest | Quest Software

You’ve completed secret agent training. You’ve travelled to the field. You’ve botched your mission.

You are being called out of the field for a performance debrief. Your last chance to redeem yourself may be to go further undercover than you’ve ever gone before - as an IT pro. Prove that you have what it takes to be a secret agent.

Watch this comedy chronicle of your latest slipups, then customize the video for a friend.

You need the Silverlight plugin to view this interactive video. Click below to upgrade your browser - it only takes a minute to install.

Get Microsoft Silverlight

Posted via web from 原宿工業大学 | Comment »

April 20, 2010
XAuth Specifications

XAuth is an open platform for extending authenticated user services across the web.

Posted via web from hdknr’s posterous | Comment »

April 13, 2010
高木浩光@自宅の日記 - ユニークIDがあれば認証ができるという幻想

元の案に書かれていた記述の何が危険思想かというと、ユーザ認証は、アプリケーションが必要としているものなのだから、アプリケーションレイヤで行うべきものであるところ、通信レイヤでもできるからといってそうしてしまうと、通信している限り常に認証されてしまうことになり、つまり、人々の「認証されない自由」が剥奪されるからである。

Posted via web from hdknr’s posterous | Comment »

April 9, 2010
IdentityBlog - Digital Identity, Privacy, and the Internet’s Missing Identity Layer

The Fourth Law of Identity

The Law of Directed Identity

A universal identity system MUST support both “omnidirectional” identifiers for use by public entities and “unidirectional” identifiers for use by private entities, thus facilitating discovery while preventing unnecessary release of correlation handles.

Technical identity is always asserted with respect to some other identity or set of identities. To make an analogy with the physical world, we can say identity is a vector, not a scalar. One special “set of identities” is that of all other identities. Other important sets exist (for example, the identies in an enterprise, some arbitrary domain, or in a peer group).

Entities that are public can have identitifiers that are invariant and well-known. These identifiers can be thought of as beacons, emitting identity to anyone who shows up - and thus being in essence “omnidirectional” (they are willing to reveal their existence to the set of all other identities).

A corporate web site with a well-known URL and public key certificate is a good example of such a public entity. There is no advantage - and in fact a great disadvantage - in changing such a public URL. It is fine for any visitor to the site to examine the public key certificate. It is similarly acceptable that everyone knows the site is there: its existence is public.

A second example of such a public entity is the “polycomm” which looms large in the scenario we chose as a backdrop to the present discussion. The polycomm sits in a conference room in an enterprise. Visitors to the conference room can see the polycomm and it offers digital services by advertising itself to those who come near it. In the thinking outlined here, it has an omni-directional identity.

On the other hand, a consumer visiting a corporate web site is able to use the identity beacon of that site to decide whether she wants to establish a relationship with it. Her system can then set up a “unidirectional” identity relation with the site by selecting a key for use with that site and no other. A unidirectional identity relation with a different site would involve fabricating a completely unrelated key. Because of this there is no handle emitted by conformant identity system technology that can be shared between sites to track or profile her activities and preferences.

Similarly, when entering a conference room furnished with a polycomm, the omnidirectional identity beacon of that polycomm can be used by the owner of a cell phone to decide whether she wants to interact with it. If she does, a short-lived “unidirectional” identity relation can be created between the cell phone and the polycomm - and used to disclose a single music preference without associating that preference with any long-lived identity whatsoever.

It is immediately evident that Bluetooth and other wireless technologies have not so far been conformant with the fourth law. This explains the privacy issues innovators in these areas are currently wrestling with. And it will be obvious to some that public key certificates have been extremely successful to the extent they were used in conformance with the fourth law (public applications).

Posted via web from 原宿工業大学 | Comment »