1 /* crypto/ui/ui.h -*- mode:C; c-file-style: "eay" -*- */
\r
2 /* Written by Richard Levitte (richard@levitte.org) for the OpenSSL
\r
5 /* ====================================================================
\r
6 * Copyright (c) 2001 The OpenSSL Project. All rights reserved.
\r
8 * Redistribution and use in source and binary forms, with or without
\r
9 * modification, are permitted provided that the following conditions
\r
12 * 1. Redistributions of source code must retain the above copyright
\r
13 * notice, this list of conditions and the following disclaimer.
\r
15 * 2. Redistributions in binary form must reproduce the above copyright
\r
16 * notice, this list of conditions and the following disclaimer in
\r
17 * the documentation and/or other materials provided with the
\r
20 * 3. All advertising materials mentioning features or use of this
\r
21 * software must display the following acknowledgment:
\r
22 * "This product includes software developed by the OpenSSL Project
\r
23 * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
\r
25 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
\r
26 * endorse or promote products derived from this software without
\r
27 * prior written permission. For written permission, please contact
\r
28 * openssl-core@openssl.org.
\r
30 * 5. Products derived from this software may not be called "OpenSSL"
\r
31 * nor may "OpenSSL" appear in their names without prior written
\r
32 * permission of the OpenSSL Project.
\r
34 * 6. Redistributions of any form whatsoever must retain the following
\r
36 * "This product includes software developed by the OpenSSL Project
\r
37 * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
\r
39 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
\r
40 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
\r
41 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
\r
42 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
\r
43 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
\r
44 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
\r
45 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
\r
46 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
\r
47 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
\r
48 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
\r
49 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
\r
50 * OF THE POSSIBILITY OF SUCH DAMAGE.
\r
51 * ====================================================================
\r
53 * This product includes cryptographic software written by Eric Young
\r
54 * (eay@cryptsoft.com). This product includes software written by Tim
\r
55 * Hudson (tjh@cryptsoft.com).
\r
62 #ifndef OPENSSL_NO_DEPRECATED
\r
63 #include <openssl/crypto.h>
\r
65 #include <openssl/safestack.h>
\r
66 #include <openssl/ossl_typ.h>
\r
72 /* Declared already in ossl_typ.h */
\r
73 /* typedef struct ui_st UI; */
\r
74 /* typedef struct ui_method_st UI_METHOD; */
\r
77 /* All the following functions return -1 or NULL on error and in some cases
\r
78 (UI_process()) -2 if interrupted or in some other way cancelled.
\r
79 When everything is fine, they return 0, a positive value or a non-NULL
\r
80 pointer, all depending on their purpose. */
\r
82 /* Creators and destructor. */
\r
84 UI *UI_new_method(const UI_METHOD *method);
\r
85 void UI_free(UI *ui);
\r
87 /* The following functions are used to add strings to be printed and prompt
\r
88 strings to prompt for data. The names are UI_{add,dup}_<function>_string
\r
89 and UI_{add,dup}_input_boolean.
\r
91 UI_{add,dup}_<function>_string have the following meanings:
\r
92 add add a text or prompt string. The pointers given to these
\r
93 functions are used verbatim, no copying is done.
\r
94 dup make a copy of the text or prompt string, then add the copy
\r
95 to the collection of strings in the user interface.
\r
97 The function is a name for the functionality that the given
\r
98 string shall be used for. It can be one of:
\r
99 input use the string as data prompt.
\r
100 verify use the string as verification prompt. This
\r
101 is used to verify a previous input.
\r
102 info use the string for informational output.
\r
103 error use the string for error output.
\r
104 Honestly, there's currently no difference between info and error for the
\r
107 UI_{add,dup}_input_boolean have the same semantics for "add" and "dup",
\r
108 and are typically used when one wants to prompt for a yes/no response.
\r
111 All of the functions in this group take a UI and a prompt string.
\r
112 The string input and verify addition functions also take a flag argument,
\r
113 a buffer for the result to end up with, a minimum input size and a maximum
\r
114 input size (the result buffer MUST be large enough to be able to contain
\r
115 the maximum number of characters). Additionally, the verify addition
\r
116 functions takes another buffer to compare the result against.
\r
117 The boolean input functions take an action description string (which should
\r
118 be safe to ignore if the expected user action is obvious, for example with
\r
119 a dialog box with an OK button and a Cancel button), a string of acceptable
\r
120 characters to mean OK and to mean Cancel. The two last strings are checked
\r
121 to make sure they don't have common characters. Additionally, the same
\r
122 flag argument as for the string input is taken, as well as a result buffer.
\r
123 The result buffer is required to be at least one byte long. Depending on
\r
124 the answer, the first character from the OK or the Cancel character strings
\r
125 will be stored in the first byte of the result buffer. No NUL will be
\r
126 added, so the result is *not* a string.
\r
128 On success, the all return an index of the added information. That index
\r
129 is usefull when retrieving results with UI_get0_result(). */
\r
130 int UI_add_input_string(UI *ui, const char *prompt, int flags,
\r
131 char *result_buf, int minsize, int maxsize);
\r
132 int UI_dup_input_string(UI *ui, const char *prompt, int flags,
\r
133 char *result_buf, int minsize, int maxsize);
\r
134 int UI_add_verify_string(UI *ui, const char *prompt, int flags,
\r
135 char *result_buf, int minsize, int maxsize, const char *test_buf);
\r
136 int UI_dup_verify_string(UI *ui, const char *prompt, int flags,
\r
137 char *result_buf, int minsize, int maxsize, const char *test_buf);
\r
138 int UI_add_input_boolean(UI *ui, const char *prompt, const char *action_desc,
\r
139 const char *ok_chars, const char *cancel_chars,
\r
140 int flags, char *result_buf);
\r
141 int UI_dup_input_boolean(UI *ui, const char *prompt, const char *action_desc,
\r
142 const char *ok_chars, const char *cancel_chars,
\r
143 int flags, char *result_buf);
\r
144 int UI_add_info_string(UI *ui, const char *text);
\r
145 int UI_dup_info_string(UI *ui, const char *text);
\r
146 int UI_add_error_string(UI *ui, const char *text);
\r
147 int UI_dup_error_string(UI *ui, const char *text);
\r
149 /* These are the possible flags. They can be or'ed together. */
\r
150 /* Use to have echoing of input */
\r
151 #define UI_INPUT_FLAG_ECHO 0x01
\r
152 /* Use a default password. Where that password is found is completely
\r
153 up to the application, it might for example be in the user data set
\r
154 with UI_add_user_data(). It is not recommended to have more than
\r
155 one input in each UI being marked with this flag, or the application
\r
156 might get confused. */
\r
157 #define UI_INPUT_FLAG_DEFAULT_PWD 0x02
\r
159 /* The user of these routines may want to define flags of their own. The core
\r
160 UI won't look at those, but will pass them on to the method routines. They
\r
161 must use higher bits so they don't get confused with the UI bits above.
\r
162 UI_INPUT_FLAG_USER_BASE tells which is the lowest bit to use. A good
\r
163 example of use is this:
\r
165 #define MY_UI_FLAG1 (0x01 << UI_INPUT_FLAG_USER_BASE)
\r
168 #define UI_INPUT_FLAG_USER_BASE 16
\r
171 /* The following function helps construct a prompt. object_desc is a
\r
172 textual short description of the object, for example "pass phrase",
\r
173 and object_name is the name of the object (might be a card name or
\r
175 The returned string shall always be allocated on the heap with
\r
176 OPENSSL_malloc(), and need to be free'd with OPENSSL_free().
\r
178 If the ui_method doesn't contain a pointer to a user-defined prompt
\r
179 constructor, a default string is built, looking like this:
\r
181 "Enter {object_desc} for {object_name}:"
\r
183 So, if object_desc has the value "pass phrase" and object_name has
\r
184 the value "foo.key", the resulting string is:
\r
186 "Enter pass phrase for foo.key:"
\r
188 char *UI_construct_prompt(UI *ui_method,
\r
189 const char *object_desc, const char *object_name);
\r
192 /* The following function is used to store a pointer to user-specific data.
\r
193 Any previous such pointer will be returned and replaced.
\r
195 For callback purposes, this function makes a lot more sense than using
\r
196 ex_data, since the latter requires that different parts of OpenSSL or
\r
197 applications share the same ex_data index.
\r
199 Note that the UI_OpenSSL() method completely ignores the user data.
\r
200 Other methods may not, however. */
\r
201 void *UI_add_user_data(UI *ui, void *user_data);
\r
202 /* We need a user data retrieving function as well. */
\r
203 void *UI_get0_user_data(UI *ui);
\r
205 /* Return the result associated with a prompt given with the index i. */
\r
206 const char *UI_get0_result(UI *ui, int i);
\r
208 /* When all strings have been added, process the whole thing. */
\r
209 int UI_process(UI *ui);
\r
211 /* Give a user interface parametrised control commands. This can be used to
\r
212 send down an integer, a data pointer or a function pointer, as well as
\r
213 be used to get information from a UI. */
\r
214 int UI_ctrl(UI *ui, int cmd, long i, void *p, void (*f)(void));
\r
217 /* Use UI_CONTROL_PRINT_ERRORS with the value 1 to have UI_process print the
\r
218 OpenSSL error stack before printing any info or added error messages and
\r
219 before any prompting. */
\r
220 #define UI_CTRL_PRINT_ERRORS 1
\r
221 /* Check if a UI_process() is possible to do again with the same instance of
\r
222 a user interface. This makes UI_ctrl() return 1 if it is redoable, and 0
\r
224 #define UI_CTRL_IS_REDOABLE 2
\r
227 /* Some methods may use extra data */
\r
228 #define UI_set_app_data(s,arg) UI_set_ex_data(s,0,arg)
\r
229 #define UI_get_app_data(s) UI_get_ex_data(s,0)
\r
230 int UI_get_ex_new_index(long argl, void *argp, CRYPTO_EX_new *new_func,
\r
231 CRYPTO_EX_dup *dup_func, CRYPTO_EX_free *free_func);
\r
232 int UI_set_ex_data(UI *r,int idx,void *arg);
\r
233 void *UI_get_ex_data(UI *r, int idx);
\r
235 /* Use specific methods instead of the built-in one */
\r
236 void UI_set_default_method(const UI_METHOD *meth);
\r
237 const UI_METHOD *UI_get_default_method(void);
\r
238 const UI_METHOD *UI_get_method(UI *ui);
\r
239 const UI_METHOD *UI_set_method(UI *ui, const UI_METHOD *meth);
\r
241 /* The method with all the built-in thingies */
\r
242 UI_METHOD *UI_OpenSSL(void);
\r
245 /* ---------- For method writers ---------- */
\r
246 /* A method contains a number of functions that implement the low level
\r
247 of the User Interface. The functions are:
\r
249 an opener This function starts a session, maybe by opening
\r
250 a channel to a tty, or by opening a window.
\r
251 a writer This function is called to write a given string,
\r
252 maybe to the tty, maybe as a field label in a
\r
254 a flusher This function is called to flush everything that
\r
255 has been output so far. It can be used to actually
\r
256 display a dialog box after it has been built.
\r
257 a reader This function is called to read a given prompt,
\r
258 maybe from the tty, maybe from a field in a
\r
259 window. Note that it's called wth all string
\r
260 structures, not only the prompt ones, so it must
\r
261 check such things itself.
\r
262 a closer This function closes the session, maybe by closing
\r
263 the channel to the tty, or closing the window.
\r
265 All these functions are expected to return:
\r
269 -1 on out-of-band events, for example if some prompting has
\r
270 been canceled (by pressing Ctrl-C, for example). This is
\r
271 only checked when returned by the flusher or the reader.
\r
273 The way this is used, the opener is first called, then the writer for all
\r
274 strings, then the flusher, then the reader for all strings and finally the
\r
275 closer. Note that if you want to prompt from a terminal or other command
\r
276 line interface, the best is to have the reader also write the prompts
\r
277 instead of having the writer do it. If you want to prompt from a dialog
\r
278 box, the writer can be used to build up the contents of the box, and the
\r
279 flusher to actually display the box and run the event loop until all data
\r
280 has been given, after which the reader only grabs the given data and puts
\r
281 them back into the UI strings.
\r
283 All method functions take a UI as argument. Additionally, the writer and
\r
284 the reader take a UI_STRING.
\r
287 /* The UI_STRING type is the data structure that contains all the needed info
\r
288 about a string or a prompt, including test data for a verification prompt.
\r
290 DECLARE_STACK_OF(UI_STRING)
\r
291 typedef struct ui_string_st UI_STRING;
\r
293 /* The different types of strings that are currently supported.
\r
294 This is only needed by method authors. */
\r
295 enum UI_string_types
\r
298 UIT_PROMPT, /* Prompt for a string */
\r
299 UIT_VERIFY, /* Prompt for a string and verify */
\r
300 UIT_BOOLEAN, /* Prompt for a yes/no response */
\r
301 UIT_INFO, /* Send info to the user */
\r
302 UIT_ERROR /* Send an error message to the user */
\r
305 /* Create and manipulate methods */
\r
306 UI_METHOD *UI_create_method(char *name);
\r
307 void UI_destroy_method(UI_METHOD *ui_method);
\r
308 int UI_method_set_opener(UI_METHOD *method, int (*opener)(UI *ui));
\r
309 int UI_method_set_writer(UI_METHOD *method, int (*writer)(UI *ui, UI_STRING *uis));
\r
310 int UI_method_set_flusher(UI_METHOD *method, int (*flusher)(UI *ui));
\r
311 int UI_method_set_reader(UI_METHOD *method, int (*reader)(UI *ui, UI_STRING *uis));
\r
312 int UI_method_set_closer(UI_METHOD *method, int (*closer)(UI *ui));
\r
313 int (*UI_method_get_opener(UI_METHOD *method))(UI*);
\r
314 int (*UI_method_get_writer(UI_METHOD *method))(UI*,UI_STRING*);
\r
315 int (*UI_method_get_flusher(UI_METHOD *method))(UI*);
\r
316 int (*UI_method_get_reader(UI_METHOD *method))(UI*,UI_STRING*);
\r
317 int (*UI_method_get_closer(UI_METHOD *method))(UI*);
\r
319 /* The following functions are helpers for method writers to access relevant
\r
320 data from a UI_STRING. */
\r
322 /* Return type of the UI_STRING */
\r
323 enum UI_string_types UI_get_string_type(UI_STRING *uis);
\r
324 /* Return input flags of the UI_STRING */
\r
325 int UI_get_input_flags(UI_STRING *uis);
\r
326 /* Return the actual string to output (the prompt, info or error) */
\r
327 const char *UI_get0_output_string(UI_STRING *uis);
\r
328 /* Return the optional action string to output (the boolean promtp instruction) */
\r
329 const char *UI_get0_action_string(UI_STRING *uis);
\r
330 /* Return the result of a prompt */
\r
331 const char *UI_get0_result_string(UI_STRING *uis);
\r
332 /* Return the string to test the result against. Only useful with verifies. */
\r
333 const char *UI_get0_test_string(UI_STRING *uis);
\r
334 /* Return the required minimum size of the result */
\r
335 int UI_get_result_minsize(UI_STRING *uis);
\r
336 /* Return the required maximum size of the result */
\r
337 int UI_get_result_maxsize(UI_STRING *uis);
\r
338 /* Set the result of a UI_STRING. */
\r
339 int UI_set_result(UI *ui, UI_STRING *uis, const char *result);
\r
342 /* A couple of popular utility functions */
\r
343 int UI_UTIL_read_pw_string(char *buf,int length,const char *prompt,int verify);
\r
344 int UI_UTIL_read_pw(char *buf,char *buff,int size,const char *prompt,int verify);
\r
347 /* BEGIN ERROR CODES */
\r
348 /* The following lines are auto generated by the script mkerr.pl. Any changes
\r
349 * made after this point may be overwritten when the script is next run.
\r
351 void ERR_load_UI_strings(void);
\r
353 /* Error codes for the UI functions. */
\r
355 /* Function codes. */
\r
356 #define UI_F_GENERAL_ALLOCATE_BOOLEAN 108
\r
357 #define UI_F_GENERAL_ALLOCATE_PROMPT 109
\r
358 #define UI_F_GENERAL_ALLOCATE_STRING 100
\r
359 #define UI_F_UI_CTRL 111
\r
360 #define UI_F_UI_DUP_ERROR_STRING 101
\r
361 #define UI_F_UI_DUP_INFO_STRING 102
\r
362 #define UI_F_UI_DUP_INPUT_BOOLEAN 110
\r
363 #define UI_F_UI_DUP_INPUT_STRING 103
\r
364 #define UI_F_UI_DUP_VERIFY_STRING 106
\r
365 #define UI_F_UI_GET0_RESULT 107
\r
366 #define UI_F_UI_NEW_METHOD 104
\r
367 #define UI_F_UI_SET_RESULT 105
\r
369 /* Reason codes. */
\r
370 #define UI_R_COMMON_OK_AND_CANCEL_CHARACTERS 104
\r
371 #define UI_R_INDEX_TOO_LARGE 102
\r
372 #define UI_R_INDEX_TOO_SMALL 103
\r
373 #define UI_R_NO_RESULT_BUFFER 105
\r
374 #define UI_R_RESULT_TOO_LARGE 100
\r
375 #define UI_R_RESULT_TOO_SMALL 101
\r
376 #define UI_R_UNKNOWN_CONTROL_COMMAND 106
\r
projects / lab.git / blob