Browse Prior Art Database

A simple registration technique to maintain identity of a host after re-installation

IP.com Disclosure Number: IPCOM000248810D
Publication Date: 2017-Jan-12
Document File: 3 page(s) / 59K

Publishing Venue

The IP.com Prior Art Database

Related People

Dhananjay Kulkarni: INVENTOR [+2]

Abstract

With the proposed technique we are providing a secure way of reissuing identity to a host and also ensuring that the identity assigned to a host cannot be stolen by other host (maliciously). We propose to make use of a special host re-registration token after reinstallation for registration in order to maintain the identity of a host.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Dhananjay Kulkarni

Gaurav Malhotra

1

© 2017 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

A simple registration technique to maintain identity of a host after

re-installation

Abstract

With the proposed technique we are providing

a secure way of reissuing identity to a host and

also ensuring that the identity assigned to a

host cannot be stolen by other host

(maliciously). We propose to make use of a

special host re-registration token after

reinstallation for registration in order to

maintain the identity of a host.

Problem Statement

In Backup products we assign an UUID to every

host that gets registered under Backup products

Domain. This UUID acts as an identity for the host

in Backup products. For a new host to be part of

Backup products domain it sends a registration

request. There are two ways of authenticating

requests

- Assign identity to all requests

- In order to identity that the request sent is

genuine, administrator supplies a registration token

along with the request.

Master server on receiving such request validates

the request and assigns a fresh UUID to such host.

Along with this UUID a certificate signed by CA with

subject as UUID is provided to the host so that host

can prove ownership of the identity. This identity is

randomly assigned UUID but once assigned it

should not get reassigned. This certificate is used

by the host for securing all Backup products

communication.

This identity can also be used to validate restore

requests. A restore request is allowed only to s host

which has same identity of the backup host.

The challenge here is that in case a host gets

reinstalled and then sends a registration request,

the master server treats this as a fresh request and

tries to assign a new fresh UUID to the host. Due to

this the host loses its earlier identity in Backup

products domain.

Publication Description

We provide an ability of creating a special token,

which has associated UUID with it in token

database. So when a host is about to be reinstalled

2

© 2017 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

or has lost its identity (UUID) for any reason, the

server administrator will mark...