 Relationships |
|
| Anonymous | Login | 2024-04-27 13:37 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0000013 | [gnupg] regular use | tweak | always | 2002-12-08 00:54 | 2006-01-09 15:30 | ||
| Reporter | phil | View Status | public | ||||
| Assigned To | ajensen | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | closed | ||||||
| Summary | 0000013: \'using insecure memory\' warning | ||||||
| Description |
I vaguely remember there is some way to get rid of the \'WARNING: using insecure memory!\' warning when using gnupg. Unfortunately, I dont remember the specifics. IIRC, it is whining that it is using memory that could potentially be swapped out to disk. If you want to actually change the code, I think you can use mmap to allocate memory, and use the mmap tweaks to truely lock the memory down, and then you could truely disable the warning as it was originally intended. |
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0000199) mike (reporter) 2003-11-09 00:50 |
\'chmod u+s /opt/csw/bin/gpg\' will fix the error. |
|
(0000200) phil (reporter) 2003-11-09 12:30 |
It would be better to fix it in the code, without requiring setuid. |
|
(0000215) ajensen (reporter) 2003-11-24 10:47 |
SUID /opt/csw/bin/gpg or (better) use 1.2.3,REV=2003.11.20. |
|
(0002923) aalmroth (reporter) 2006-01-09 15:30 |
Closing report |
| Copyright © 2000 - 2008 Mantis Group |  |
