bontibon/digitalocean-alpine 164
Script to install Alpine Linux on a Digital Ocean droplet
bontibon/kjv 86
Read the Word of God from your terminal
time tracker script to help track time
PAM authenticator for grpc-enabled Mumble servers
a collection of simple browser games
Opens a Wikipedia article at random intervals
Final project for COMP 2663
Quick and dirty Protocol Buffer example
push eventlayeh/gopher-lfs
commit sha a501306817ed1b0c24d49fe3d2746283569674fc
add target attribute Closes #3
commit sha 06fd7e4d350bf87d06edc27f1c5dd6cad02baee1
simplify Lua table raw getters, setters
push time in 6 days
PR closed layeh/gopher-lfs
https://keplerproject.github.io/luafilesystem/manual.html manual symlinkattributes method should target attr
pr closed time in 6 days
issue closedlayeh/murmur-cli
Hi, I am really curious about this gRPC protocol that seems easier to handle than zeroc-ice but I could not manage to get the package to install:
$ go get -u layeh.com/murmur-cli
$ murmur-cli
murmur-cli: command not found
$ go version
go version go1.10.4 linux/amd64
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
Attaching the output from go get -v -u layeh.com/murmur-cli
verbose.txt
closed time in 17 days
yquemener
issue commentlayeh/murmur-cli
Go binaries are likely installed in a location that is not part of your path. See go help install:
Executables are installed in the directory named by the GOBIN environment variable, which defaults to $GOPATH/bin or $HOME/go/bin if the GOPATH environment variable is not set.
comment created time in 17 days
push eventbontibon/kjv
commit sha 281bbd97ba215d02bd19915c4b44c7725b97ad1a
explicitly set tar output file to standard output Closes #12
push time in 21 days
PR closed bontibon/kjv
Tested in Manjaro Linux & FreeBSD. When paired with the last commit, it fixes runtime errors in BSD.
pr closed time in 21 days
push eventbontibon/kjv
commit sha 42e19d88b6bb393bc194b67cf1f34669cef6daa5
explicitly set tar input file to standard input Closes #11
push time in 22 days
issue closedbontibon/kjv
FreeBSD Errors "Failed to open '/dev/sa0'"
I have tried tinkering with the tar command in the Makefile before reinstalling kjv multiple times, but I am constantly stuck with the following pair of error messages when trying to actually run 'kjv' (e.g. typing 'kjv mark 1'):
Error opening archive: Failed to open '/dev/sa0'
tar: Error opening archive: Failed to open 'dev/sa0'
Thank you for the help. I have used kjv for a long time in GNU/Linux. I am brand new to FreeBSD, however, and all my web searches and little tinkers to try to fix this have come up dry so far.
God bless.
closed time in 22 days
historical-theology
push eventlayeh/radius
commit sha d62a6e0a181915aa4d007265bc81ee02531e7baa
vendor RFC, vendors dictionary files
push time in a month
push eventlayeh/gumble
commit sha 146f9205029b73783dbd79043c4fc5247d8c425d
add logo
push time in a month
issue commentlayeh/radius
Allow radius response to timeout
First, the current default is insensible, as it doesn't set any timeout which means it will block forever. This is a real problem for protocol such as UDP where no acknowledgement is promised. This caused a bug in my program and it was pretty hard to trace it. I think that to make the library more user friendly and require less internal knowledge of the library internals it would be better to set reasonable timeout and let the user optimise it if needed.
This is only because context.Background() was used, no? Would have adding a sensible timeout to the context passed to the function solved this issue for you?
Second, the context setting is for the whole function call, and the response specific timeout is more granular.
Is there a real-world scenario why such a granular setting would be required? (I would simply like to avoid making the API surface larger if it can be helped).
comment created time in a month
issue closedlayeh/radius
Allow radius response to timeout
Enhancement: currently after RADIUS request is sent (via Client.Exchange()) the response to the requests blocks. In order to allow the response to timeout, a ReadTimeout can be set on the connection.
closed time in a month
ofirm93
issue commentlayeh/radius
Allow radius response to timeout
This is already supported with context:
ctx, done := context.WithTimeout(context.Background(), time.Second)
defer done()
resp, err := client.Exchange(ctx, req, server.Addr)
comment created time in a month
push eventlayeh/radius
commit sha df567032bb2c2060ef7fe4afe0a22fc0da365a85
add rfc6677
commit sha de94a2aa0a2de140be72e4a8dc0cd0ee7643ba0d
add rfc6572
commit sha 2b3c75865c20eb22199e87c02cc52242ccb300c9
add rfc6519
commit sha 156c8511744b494c46a1d4e94762bb929325d412
add rfc5447
commit sha 63a7f112519d9a81af21877587af5edbf481b9ae
add rfc5904
commit sha 29d5ceaf96ecb72c4f56c721f965f3087d8b6020
add rfc4675
commit sha 6fa01a13882fa441521198035bf1e64e735f73fd
add rfc7055
commit sha 2801bc3084b78eb1406ef086404b8d7b7ab2f1f6
add rfc7268
push time in 2 months
push eventlayeh/radius
commit sha d06650ea3e520426d8125d229645f68aea9213c0
add PacketServer.ErrorLog Closes #76 Closes #77
push time in 2 months
PR closed layeh/radius
Adding a simple logger to PacketServer. Implementation mirrors net/http package internals. If a caller doesn't set a logger on the PacketServer struct, the 'log' package default logger will be used. The log package default logger just dumps to stdout.
pr closed time in 2 months
issue commentlayeh/radius
The logging would only be for things like errors, not debugging information like successful connections or packet responses.
The net/http.*Server just uses the log package for this (see net/http.*Server.ErrorLog). What are you thoughts on that?
comment created time in 2 months
push eventlayeh/radius
commit sha 13220954963490f7c76183332cbd33b1da6e1c0a
fix invalid attributes being included by Attributes.encodeTo
commit sha 0492ccb85c52a15202ebc7c38ecefd4b5f87ca7d
add (*Packet).MarshalBinary() Closes #75
push time in 2 months
PR closed layeh/radius
It is sometimes useful to be able to access the Packet struct in byte form. One example of this is for validating MessageAuthenticator attributes (see RFC2869) from a Response packet.
Encode can modify the Authenticator field of a packet, breaking reliable validation ability when converting a Packet off the wire back into Bytes. The MarshalBinary method makes it simple to fetch a Packet in byte form without the packet being modified. MarshalBinary also satisfies the BinaryMarshaller interface found in the standard Go encoding package. This may add some flexibility to users of this code base.
Alternatively, if this approach is disliked, perhaps there could be a Raw field added to the Packet struct that is populated upon Parse and Encode calls.
pr closed time in 2 months
push eventlayeh/radius
commit sha a9ad15de79b9b7ddb772eaf6d4fad9109e69172c
reduce logo size in README
push time in 2 months
push eventlayeh/radius
commit sha 4b6cc7756d169267b0b230c6fd9a85388c93665a
add new logo
push time in 2 months
issue closedlayeh/gopher-luar
What about pointers, like this print( sql:Table (inspection task): count (NIL))
What about pointers, like this
print( sql:Table (inspection task): count (NIL))
closed time in 2 months
dukv2001
issue commentlayeh/gopher-luar
What about pointers, like this print( sql:Table (inspection task): count (NIL))
I'm sorry, I don't understand your question.
comment created time in 2 months
push eventlayeh/radius
commit sha 3763b3784f20e6dea9458b6a3438f0d045cdf905
add rfc4849
commit sha 61b08032e402fd3373fbb93f584b731cff87ee16
add rfc5090
commit sha 7bfb11a8d6efe6ba7184c6e20af8789353fb8914
add rfc5580
commit sha 99b3878d251841cd24c051341f6b30eb3b8c9cdc
add rfc5607
push time in 2 months
push eventlayeh/radius
commit sha fc7f8832aaab7cda54ffdcba453472b91429f753
add rfc3580
commit sha 22353ce9faa8267af809a67185503846035775f6
add rfc4072
commit sha 30f39acc0189ec95d21fe1888a272b96f1b7f1d0
add rfc4603
push time in 2 months
PR closed layeh/radius
- Add generated code for Microsoft extensions to the CHAP protocol family, using the dictionary from Freeradius.
- Add implementations for some functions described in rfc2759 and rfc3079
- Change handling of the
saltparameter ofNewTunnelPassword
With these patches, it is possible to handle requests from clients that use the MS-CHAPv2 protocol and that expect Send/Recv MPPE keys. One such device is the Unify Security Gateway (USG).
pr closed time in 2 months
pull request commentlayeh/radius
Add support for MS-CHAPv2 and MPPE
I've merged your PR into master. Please give it a test to ensure everything is working as expected. Thanks!
comment created time in 2 months
push eventlayeh/radius
commit sha d510fa7776264f9a13638cdb7b34850b60ad9866
add Microsoft vendor support This is needed for parsing packet details from the MS-CHAP family.
commit sha b96a9baf00cf71acb3778e6ab4fe6c93e2a6cc46
add implementation for MS-CHAPv2 (RFC 2759) This patch implements the necessary functions to handle MS-CHAPv2 authentication sequences, as described in RFC 2759.
commit sha 39bb14338862d84fe4bc481bfd817abf163446d8
add functions for MPPE handshakes (RFC 3079) This patch adds support for adding MPPE send/recv keys that are attached to MSCHAPv2 response packets, as described by RFC 3079. The results from MakeKey() can be used as input for NewTunnelPassword(). Code is tested with examples from section 3.5 of the RFC.
commit sha 013e2f8559d7f63e53dd2d400472aa07c068c3ef
add example server that shows how to use MSCHAPv2 authentication
commit sha f26736460a5c9fcb35df55347ef9d698c1f12efc
clean up RFC 2759, RFC 3079, vendors/microsoft
push time in 2 months
push eventlayeh/radius
commit sha 704f94c9e1557039667ff618437a7c1437186679
fix generated tunnel password salt sometimes being invalid Closes #69
push time in 2 months
PR closed layeh/radius
RFC2868 section 3.5 requires that the MSB in the first byte of the salt is set. This was already checked by the core RADIUS code but the RFC2868 setter/adder that generates the salt randomly did not pay attention to this requirement.
Also added some test code to test this.
pr closed time in 2 months