Follow-up Comment #3, sr #108837 (project freeipmi):
Can you show us the build issues with libgcrypt, the version you're using, and
create a bug about it? There are presently no known porting issues with it,
so this may be new.
Lack of encryption effectively means that IPMI encryption using IPMI 2.0 (i.e.
"LAN_2_0" for driver-type) cannot be used. Non-encrypted network
communication can be used (via IPMI 1.5 "LAN" or non-encrypted IPMI 2.0
connections), which is probably fine for sensors and power control and what
not (which very few would likely care for the sensitivity of such data).
The most notable thing that cannot be used would be serial-over-lan or console
access, such as with ipmiconsole, with encryption. That is communication that
users will care that network traffic is encrypted.
See the -I option in most tools to see about the unencrypted ciphers that can
be used.
It should probably be noted that use of non-encrypted ciphers may depend on
motherboard. Some motherboards do not allow it at all.
All tools that are used locally on the local machine should not be affected at
all.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?108837>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-devel
