seccure insecure processing

Bug #808336 reported by udippel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seccure (Ubuntu)
New
Undecided
Unassigned

Bug Description

By default, seccure is written to run in locked memory to prevent swapping out sensitive data.
Since some unknown time, for reasons unknown to me, this fails, because the memory cannot be allocated, meaning the process is run, if need be using swap space.
Remedy: seccure 0.4 does allocate locked memory properly. It is suggested to effectively bump up the version, respectively 0.3-3 to a new patch level.

$ seccure-dh -v
WARNING: Cannot obtain memory lock: Cannot allocate memory.
Assuming curve p160.
VERSION: 0.3
CURVE: secp160r1
Pass the following key to your peer: %Wb0PQDh[Dx-F~K~9Ip~?n+@5
Enter your peer's key:
$

So it runs, in whichever location.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: seccure (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Jul 10 20:24:12 2011
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: seccure
UpgradeStatus: Upgraded to natty on 2011-04-29 (71 days ago)

security vulnerability: yes → no
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.