Collections of packages and tools for working with Go programming language. http://git.kilabit.info/pakakeh.go/atom?h=v0.28.0 2021-07-06T02:38:15Z 2021-07-06T02:38:15Z Shulhan ms@kilabit.info 2021-07-06T02:38:15Z urn:sha1:17963c194c09db28eff8c52f3da14c9879c8e390 === Breaking changes * lib/ssh: rename method Get to ScpGet and Put to ScpPut This changes is to make clear that the methods to copy the files, either from local or from remote, is using the "scp" through exec package, not using the native SSH file transfer protocol. While at it, use consistent log prefix for error message. * ssh: rename the NewClient function to NewClientFromConfig This is to differentiate it with x/crypto ssh package that have the same function name. * ssh: move the config parser to subpackage "config" There are two reasons for moving to sub-package. First, the code for parsing the ssh_config(5) take almost 99% of the lines in the ssh package. Second, in case we want to submit the code to upstream, golang.org/x/crypto, we need the package to be independent, less external dependencies as possible. * http: remove the Memfs field from Server Now that Options field has been exported, we did not need to have duplicate Memfs, so this field is removed in favor of Options.Memfs. === Enhancements * websocket: export the Options field on the Server Previously, the Options field is not exported to prevent user from changing it once it set through NewServer() function. This changes export the Options field to allow user of Server access its values. We can create a method on server to return read-only options, but that will over complicated the Server API. * http: export the Options field on the Server Previously, the Options field is not exported to prevent user from changing it once it set through NewServer() function. This changes export the Options field to allow user of Server access its values. We can create a method on server to return read-only options, but that will over complicated the Server API. * websocket: store all the handshake headers to Handshake.Header Previously only non-required headers are stored in the Handshake Header field, while the required header value stored on their respective fields. This commit store all request header key and values into the Header field. 2021-07-04T17:34:38Z Shulhan ms@kilabit.info 2021-07-04T17:32:13Z urn:sha1:c0fc44c33a7a359309ea147908289a0add74b694 This changes is to make clear that the methods to copy the files, either from local or from remote, is using the "scp" through exec package, not using the native SSH file transfer protocol. While at it, use consistent log prefix for error message. 2021-07-04T17:02:16Z Shulhan ms@kilabit.info 2021-07-04T17:00:12Z urn:sha1:114faf30cb2f9934c7656014e9109c383eea49a2 This will allow seamless integration with the x/crypto/ssh Client type. 2021-07-04T17:02:15Z Shulhan ms@kilabit.info 2021-07-04T16:55:32Z urn:sha1:24b08a2c40f0587246fcaaa193e6accfc7ad8197 This is to differentiate it with x/crypto ssh package that have the same function name. 2021-07-04T17:02:15Z Shulhan ms@kilabit.info 2021-07-04T11:46:48Z urn:sha1:6c50a17b71b8a33cdd37a119cbb3157411a221e6 There are two reasons for moving to sub-package. First, the code for parsing the ssh_config(5) take almost 99% of the lines in the ssh package. Second, in case we want to submit the code to upstream, golang.org/x/crypto, we need the package to be independent, less external dependencies as possible. 2021-06-26T13:48:33Z Shulhan ms@kilabit.info 2021-06-26T13:48:33Z urn:sha1:6edca531e2a08ee736d58c5819f21201d9520eeb Now that Options field has been exported, we did not need to have duplicate Memfs, so this field is removed in favor of Options.Memfs. 2021-06-26T12:47:48Z Shulhan ms@kilabit.info 2021-06-26T12:47:48Z urn:sha1:1dd82a36485b161d855be345af94e7f032aa10ed 2021-06-26T12:40:15Z Shulhan ms@kilabit.info 2021-06-26T12:40:15Z urn:sha1:11fb91f7b1dcbccb26a8d8daaf43df15ff9adf9c 2021-06-26T12:32:35Z Shulhan ms@kilabit.info 2021-06-26T12:32:35Z urn:sha1:c124ae94676bec1188ea168685429c9299b4dcbe Previously, the Options field is not exported to prevent user from changing it once it set throught NewServer() function. This changes export the Options field to allow user of Server access its values. We can create a method on server to return read-only options, but that will over complicated the Server API. 2021-06-26T12:32:03Z Shulhan ms@kilabit.info 2021-06-26T12:30:57Z urn:sha1:8909262650f1687a7f8d79082622b063fe31aea6 Previously, the Options field is not exported to prevent user from changing it once it set throught NewServer() function. This changes export the Options field to allow user of Server access its values. We can create a method on server to return read-only options, but that will over complicated the Server API.