Serial-over-lan (sol) client for Intel AMT
AMT (included in Intel vPro and Centrino Pro) provides out-of-band
(OOB) management for Desktops and Laptops, using an agent integrated in
the network adapter and in the motherboard.
Serial-over-lan provides a (secure) way to connect a remote computer,
through a pseudo serial interface.
This package provide 2 terminals (amtterm and gamt) to connect to that
pseudo serial interface from a remote computer. amttool is a perl
script to gather informations about and remotely control AMT managed
computers.
Authors:
--------
Gerd Hoffmann
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / amtterm
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout utilities/amtterm && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| amtterm-1.6.tar.gz | 0000040804 39.8 KB | |
| amtterm.changes | 0000002908 2.84 KB | |
| amtterm.spec | 0000002765 2.7 KB |
Revision 7 (latest revision is 10)
Michael Vetter (jubalh)
accepted
request 624830
from
Markos Chandras (markoschandras)
(revision 7)
- Version bump to 1.6. Some of the changes are * move wsman stuff * switch to vte 2.91 * fix version * Add note about AMT 9.0 * switch over to use gtk3 - Remove patches which have made it upstream * amtterm-fix-version.patch * amtterm-fixup-indentation.patch * amtterm-git0ece513.patch * amtterm-gtk3.patch * amtterm-note-about-amt90.patch * amtterm-wsman-password.patch * amtterm-wsman.patch - spec-cleaner fixes - Split graphical UI to a separate subpackage
Comments 1
amtterm no longer works with vPro/AMT 12.0. On my Dell Optiplex 7070 and HP 800 G5 with 12.0.0.0010/ME 12.0.39.1431 the authentication step always fails:
amtterm: NONE -> CONNECT (connection to host) ipv4 192.168.1.43 [192.168.1.43] 16994 open amtterm: CONNECT -> INIT (redirection initialization) amtterm: INIT -> AUTH (session authentication) amtterm: AUTH -> ERROR (failure) amtterm: ERROR: session authentication failed
All other tools like wsman, wsamt, amtctrl still work fine, kvm with any vnc client does, too, just amtterm doesn't.
Gerd Hoffmann, the author of amtterm, says he doesn't have time (and no vPro hardware) at the moment to look into this...