line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
package Net::Whois::Object::KeyCert; |
2
|
|
|
|
|
|
|
|
3
|
1
|
|
|
1
|
|
83880
|
use strict; |
|
1
|
|
|
|
|
12
|
|
|
1
|
|
|
|
|
36
|
|
4
|
1
|
|
|
1
|
|
6
|
use warnings; |
|
1
|
|
|
|
|
2
|
|
|
1
|
|
|
|
|
38
|
|
5
|
1
|
|
|
1
|
|
5
|
use base qw/Net::Whois::Object/; |
|
1
|
|
|
|
|
3
|
|
|
1
|
|
|
|
|
618
|
|
6
|
|
|
|
|
|
|
|
7
|
|
|
|
|
|
|
####################################################################################### |
8
|
|
|
|
|
|
|
# The following lines where auto-generated by 'perl whois_to_attribute.pl KeyCert' |
9
|
|
|
|
|
|
|
|
10
|
|
|
|
|
|
|
# % This is the RIPE Database query service. |
11
|
|
|
|
|
|
|
# % The objects are in RPSL format. |
12
|
|
|
|
|
|
|
# % |
13
|
|
|
|
|
|
|
# % The RIPE Database is subject to Terms and Conditions. |
14
|
|
|
|
|
|
|
# % See http://www.ripe.net/db/support/db-terms-conditions.pdf |
15
|
|
|
|
|
|
|
# |
16
|
|
|
|
|
|
|
# key-cert: [mandatory] [single] [primary/lookup key] |
17
|
|
|
|
|
|
|
# method: [generated] [single] [ ] |
18
|
|
|
|
|
|
|
# owner: [generated] [multiple] [ ] |
19
|
|
|
|
|
|
|
# fingerpr: [generated] [single] [inverse key] |
20
|
|
|
|
|
|
|
# certif: [mandatory] [multiple] [ ] |
21
|
|
|
|
|
|
|
# org: [optional] [multiple] [inverse key] |
22
|
|
|
|
|
|
|
# remarks: [optional] [multiple] [ ] |
23
|
|
|
|
|
|
|
# notify: [optional] [multiple] [inverse key] |
24
|
|
|
|
|
|
|
# admin-c: [optional] [multiple] [inverse key] |
25
|
|
|
|
|
|
|
# tech-c: [optional] [multiple] [inverse key] |
26
|
|
|
|
|
|
|
# mnt-by: [mandatory] [multiple] [inverse key] |
27
|
|
|
|
|
|
|
# created: [generated] [single] [ ] |
28
|
|
|
|
|
|
|
# last-modified: [generated] [single] [ ] |
29
|
|
|
|
|
|
|
# source: [mandatory] [single] [ ] |
30
|
|
|
|
|
|
|
# |
31
|
|
|
|
|
|
|
# % This query was served by the RIPE Database Query Service version 1.99 (HEREFORD) |
32
|
|
|
|
|
|
|
# |
33
|
|
|
|
|
|
|
# |
34
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'primary', [ 'key_cert' ] ); |
35
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'mandatory', [ 'key_cert', 'certif', 'mnt_by', 'source' ] ); |
36
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'optional', [ 'method', 'owner', 'fingerpr', 'org', 'remarks', 'notify', 'admin_c', 'tech_c', 'created', 'last_modified' ] ); |
37
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'single', [ 'key_cert', 'method', 'fingerpr', 'created', 'last_modified', 'source' ] ); |
38
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'multiple', [ 'owner', 'certif', 'org', 'remarks', 'notify', 'admin_c', 'tech_c', 'mnt_by' ] ); |
39
|
|
|
|
|
|
|
|
40
|
|
|
|
|
|
|
# End of auto-generated lines |
41
|
|
|
|
|
|
|
####################################################################################### |
42
|
|
|
|
|
|
|
|
43
|
|
|
|
|
|
|
=head1 NAME |
44
|
|
|
|
|
|
|
|
45
|
|
|
|
|
|
|
Net::Whois::Object::KeyCert - an object representation of the RPSL KeyCert block |
46
|
|
|
|
|
|
|
|
47
|
|
|
|
|
|
|
=head1 DESCRIPTION |
48
|
|
|
|
|
|
|
|
49
|
|
|
|
|
|
|
A key-cert object is a database public key certificate that is stored |
50
|
|
|
|
|
|
|
on the server and may be used with a mntner object for authentication |
51
|
|
|
|
|
|
|
when performing updates. Currently only PGP keys are supported. |
52
|
|
|
|
|
|
|
|
53
|
|
|
|
|
|
|
=head1 METHODS |
54
|
|
|
|
|
|
|
|
55
|
|
|
|
|
|
|
=head2 B |
56
|
|
|
|
|
|
|
|
57
|
|
|
|
|
|
|
Constructor for the Net::Whois::Object::InetRtr class |
58
|
|
|
|
|
|
|
|
59
|
|
|
|
|
|
|
=cut |
60
|
|
|
|
|
|
|
|
61
|
|
|
|
|
|
|
sub new { |
62
|
1
|
|
|
1
|
1
|
4
|
my ( $class, @options ) = @_; |
63
|
|
|
|
|
|
|
|
64
|
1
|
|
|
|
|
4
|
my $self = bless {}, $class; |
65
|
1
|
|
|
|
|
10
|
$self->_init(@options); |
66
|
|
|
|
|
|
|
|
67
|
1
|
|
|
|
|
3
|
return $self; |
68
|
|
|
|
|
|
|
} |
69
|
|
|
|
|
|
|
|
70
|
|
|
|
|
|
|
=head2 B |
71
|
|
|
|
|
|
|
|
72
|
|
|
|
|
|
|
Accessor to the key_cert attribute. |
73
|
|
|
|
|
|
|
Accepts an optional key_cert value, always return the current key_cert value. |
74
|
|
|
|
|
|
|
|
75
|
|
|
|
|
|
|
For PGP KeyCert objects, the value of the key_cert attribute must be |
76
|
|
|
|
|
|
|
PGP-"key-id". These keys are compliant with the Open PGP Internet Standard. |
77
|
|
|
|
|
|
|
|
78
|
|
|
|
|
|
|
For X.509 KeyCert objects, the database software assigns this value as |
79
|
|
|
|
|
|
|
X.509-n. Here, 'n' is the next available number assigned by the software. If |
80
|
|
|
|
|
|
|
you want to create an X.509 KeyCert object, you should specify the value as |
81
|
|
|
|
|
|
|
AUTO-xx. If you delete an X.509 KeyCert object, it is not possible to |
82
|
|
|
|
|
|
|
recreate it with the same name. |
83
|
|
|
|
|
|
|
|
84
|
|
|
|
|
|
|
=head2 B |
85
|
|
|
|
|
|
|
|
86
|
|
|
|
|
|
|
Accessor to the method attribute. |
87
|
|
|
|
|
|
|
Accepts an optional method, always return the current method value. |
88
|
|
|
|
|
|
|
|
89
|
|
|
|
|
|
|
The method attribute is generated by the software. |
90
|
|
|
|
|
|
|
It is not necessary to include this attribute when you create or |
91
|
|
|
|
|
|
|
modify this object. If it is supplied, the software will check the value. |
92
|
|
|
|
|
|
|
If necessary the software will replace the supplied value with generated |
93
|
|
|
|
|
|
|
value. In this case a warning is returned to the user. |
94
|
|
|
|
|
|
|
|
95
|
|
|
|
|
|
|
=head2 B |
96
|
|
|
|
|
|
|
|
97
|
|
|
|
|
|
|
Accessor to the owner attribute. |
98
|
|
|
|
|
|
|
Accepts an optional owner to be added to the owner array, |
99
|
|
|
|
|
|
|
always return the current owner array. |
100
|
|
|
|
|
|
|
|
101
|
|
|
|
|
|
|
The owner attribute is generated by the software. |
102
|
|
|
|
|
|
|
It is not necessary to include this attribute when you create or |
103
|
|
|
|
|
|
|
modify this object. If it is supplied, the software will check the value. |
104
|
|
|
|
|
|
|
If necessary the software will replace the supplied value with generated |
105
|
|
|
|
|
|
|
value. In this case a warning is returned to the user. |
106
|
|
|
|
|
|
|
|
107
|
|
|
|
|
|
|
=head2 B |
108
|
|
|
|
|
|
|
|
109
|
|
|
|
|
|
|
Accessor to the fingerpr attribute. |
110
|
|
|
|
|
|
|
Accepts an optional fingerpr, always return the current fingerpr. |
111
|
|
|
|
|
|
|
|
112
|
|
|
|
|
|
|
The fingerpr attribute is generated by the software. |
113
|
|
|
|
|
|
|
It is not necessary to include this attribute when you create or |
114
|
|
|
|
|
|
|
modify this object. If it is supplied, the software will check the value. |
115
|
|
|
|
|
|
|
If necessary the software will replace the supplied value with generated |
116
|
|
|
|
|
|
|
value. In this case a warning is returned to the user. |
117
|
|
|
|
|
|
|
|
118
|
|
|
|
|
|
|
=head2 B |
119
|
|
|
|
|
|
|
|
120
|
|
|
|
|
|
|
Accessor to the certif attribute. |
121
|
|
|
|
|
|
|
Accepts an optional certif to be added to the certif array, |
122
|
|
|
|
|
|
|
always return the current certif array. |
123
|
|
|
|
|
|
|
|
124
|
|
|
|
|
|
|
The certif attribute contains the public key. The value of the public key |
125
|
|
|
|
|
|
|
should be supplied either using multiple certif attributes, or in one |
126
|
|
|
|
|
|
|
certif attribute split over several lines. In the first case, this is |
127
|
|
|
|
|
|
|
easily done by exporting the key from your local key ring in ASCII armored |
128
|
|
|
|
|
|
|
format and adding the string certif to the start of each line of the key. |
129
|
|
|
|
|
|
|
In the second case, line continuation should be used to represent an ASCII |
130
|
|
|
|
|
|
|
armored format of the key. All the lines of the exported key must be included, |
131
|
|
|
|
|
|
|
as well as the start/end markers and the empty line which separates the header |
132
|
|
|
|
|
|
|
from the key body. |
133
|
|
|
|
|
|
|
|
134
|
|
|
|
|
|
|
=head2 B |
135
|
|
|
|
|
|
|
|
136
|
|
|
|
|
|
|
Accessor to the remarks attribute. |
137
|
|
|
|
|
|
|
Accepts an optional remark to be added to the remarks array, |
138
|
|
|
|
|
|
|
always return the current remarks array. |
139
|
|
|
|
|
|
|
|
140
|
|
|
|
|
|
|
General remarks. May include a URL or email address. |
141
|
|
|
|
|
|
|
|
142
|
|
|
|
|
|
|
=head2 B |
143
|
|
|
|
|
|
|
|
144
|
|
|
|
|
|
|
Accessor to the org attribute. |
145
|
|
|
|
|
|
|
Accepts an optional org value to be added to the org array, |
146
|
|
|
|
|
|
|
always return the current org array. |
147
|
|
|
|
|
|
|
|
148
|
|
|
|
|
|
|
The organisation entity this object is bound to. |
149
|
|
|
|
|
|
|
|
150
|
|
|
|
|
|
|
=head2 B |
151
|
|
|
|
|
|
|
|
152
|
|
|
|
|
|
|
Accessor to the notify attribute. |
153
|
|
|
|
|
|
|
Accepts an optional notify value to be added to the notify array, |
154
|
|
|
|
|
|
|
always return the current notify array. |
155
|
|
|
|
|
|
|
|
156
|
|
|
|
|
|
|
The email address to which notifications of changes to this object should be |
157
|
|
|
|
|
|
|
sent. |
158
|
|
|
|
|
|
|
|
159
|
|
|
|
|
|
|
=head2 B |
160
|
|
|
|
|
|
|
|
161
|
|
|
|
|
|
|
Accessor to the admin_c attribute. |
162
|
|
|
|
|
|
|
Accepts an optional contact to be added to the admin_c array, |
163
|
|
|
|
|
|
|
always return the current admin_c array. |
164
|
|
|
|
|
|
|
|
165
|
|
|
|
|
|
|
The NIC-handle of an on-site contact Person object. As more than one person |
166
|
|
|
|
|
|
|
often fulfills a role function, there may be more than one admin_c listed. |
167
|
|
|
|
|
|
|
|
168
|
|
|
|
|
|
|
An administrative contact (admin_c) must be someone who is physically |
169
|
|
|
|
|
|
|
located at the site of the network. |
170
|
|
|
|
|
|
|
|
171
|
|
|
|
|
|
|
=head2 B |
172
|
|
|
|
|
|
|
|
173
|
|
|
|
|
|
|
Accessor to the tech_c attribute. |
174
|
|
|
|
|
|
|
Accepts an optional contact to be added to the tech_c array, |
175
|
|
|
|
|
|
|
always return the current tech_c array. |
176
|
|
|
|
|
|
|
|
177
|
|
|
|
|
|
|
The NIC-handle of a technical contact Person or Role object. As more than |
178
|
|
|
|
|
|
|
one person often fulfills a role function, there may be more than one tech_c |
179
|
|
|
|
|
|
|
listed. |
180
|
|
|
|
|
|
|
|
181
|
|
|
|
|
|
|
A technical contact (tech_c) must be a person responsible for the |
182
|
|
|
|
|
|
|
day-to-day operation of the network, but does not need to be |
183
|
|
|
|
|
|
|
physically located at the site of the network. |
184
|
|
|
|
|
|
|
|
185
|
|
|
|
|
|
|
=head2 B |
186
|
|
|
|
|
|
|
|
187
|
|
|
|
|
|
|
Accessor to the mnt_by attribute. |
188
|
|
|
|
|
|
|
Accepts an optional mnt_by value to be added to the mnt_by array, |
189
|
|
|
|
|
|
|
always return the current mnt_by array. |
190
|
|
|
|
|
|
|
|
191
|
|
|
|
|
|
|
Lists a registered Mntner used to authorize and authenticate changes to this |
192
|
|
|
|
|
|
|
object. |
193
|
|
|
|
|
|
|
|
194
|
|
|
|
|
|
|
|
195
|
|
|
|
|
|
|
=head2 B |
196
|
|
|
|
|
|
|
|
197
|
|
|
|
|
|
|
Accessor to the changed attribute. |
198
|
|
|
|
|
|
|
Accepts an optional changed value to be added to the changed array, |
199
|
|
|
|
|
|
|
always return the current changed array. |
200
|
|
|
|
|
|
|
|
201
|
|
|
|
|
|
|
The email address of who last updated the database object and the date it |
202
|
|
|
|
|
|
|
occurred. |
203
|
|
|
|
|
|
|
|
204
|
|
|
|
|
|
|
Every time a change is made to a database object, this attribute will show |
205
|
|
|
|
|
|
|
the email address of the person who made those changes. |
206
|
|
|
|
|
|
|
Please use the address format specified in RFC 822 - Standard for |
207
|
|
|
|
|
|
|
the Format of ARPA Internet Text Message and provide the date |
208
|
|
|
|
|
|
|
format using one of the following two formats: YYYYMMDD or YYMMDD. |
209
|
|
|
|
|
|
|
|
210
|
|
|
|
|
|
|
=head2 B |
211
|
|
|
|
|
|
|
|
212
|
|
|
|
|
|
|
Accessor to the source attribute. |
213
|
|
|
|
|
|
|
Accepts an optional source, always return the current source. |
214
|
|
|
|
|
|
|
|
215
|
|
|
|
|
|
|
The database where the object is registered. |
216
|
|
|
|
|
|
|
|
217
|
|
|
|
|
|
|
=cut |
218
|
|
|
|
|
|
|
|
219
|
|
|
|
|
|
|
1; |