gogs

gogs

A painless self-hosted Git service

Member Since 7 years ago

Wildest Dream

Experience Points
0
follower
Lessons Completed
0
follow
Best Reply Awards
16
repos
Activity
Jan
19
10 hours ago
started
started time in 3 hours ago
started
started time in 4 hours ago
started
started time in 4 hours ago
Jan
18
1 day ago
started
started time in 10 hours ago
started
started time in 10 hours ago
started
started time in 14 hours ago
started
started time in 16 hours ago
started
started time in 16 hours ago
started
started time in 17 hours ago
started
started time in 17 hours ago
Activity icon
fork

DevenLu forked gogs/gogs

⚡ Gogs is a painless self-hosted Git service
DevenLu MIT License Updated
fork time in 17 hours ago
started
started time in 17 hours ago
started
started time in 20 hours ago
started
started time in 21 hours ago
Activity icon
issue

unknwon issue comment gogs/gogs

unknwon
unknwon

error: kex_exchange_identification in logs

Gogs version

0.13.0+dev

Git version

  • Server: 2.32.0
  • Client: n/a

Operating system

Docker version 20.10.5+dfsg1, build 55c4c88 on Debian 11.2 (armv7l)

Database

postgresql-13.4-2

Describe the bug

Once a minute I see the following posted to logs:

Jan 16 03:25:43 sshd[124]: error: kex_exchange_identification: Connection closed by remote host
Jan 16 03:25:43 sshd[124]: Connection closed by 127.0.0.1 port 34959

ssh access works. Just curious what the errors are.

The two errors appear as if scheduled to run every 30 to 60 seconds.

To reproduce

Install gogs via Docker

Expected behavior

Expect no errors that lead you believe somebody is trying to connect to the service

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
unknwon
unknwon

This may related to how Docker image was constructed for the 0.13 branch (received users on 0.12 not seeing this behavior). Re-opening in case there are some clues.

Activity icon
issue

unknwon issue gogs/gogs

unknwon
unknwon

error: kex_exchange_identification in logs

Gogs version

0.13.0+dev

Git version

  • Server: 2.32.0
  • Client: n/a

Operating system

Docker version 20.10.5+dfsg1, build 55c4c88 on Debian 11.2 (armv7l)

Database

postgresql-13.4-2

Describe the bug

Once a minute I see the following posted to logs:

Jan 16 03:25:43 sshd[124]: error: kex_exchange_identification: Connection closed by remote host
Jan 16 03:25:43 sshd[124]: Connection closed by 127.0.0.1 port 34959

ssh access works. Just curious what the errors are.

The two errors appear as if scheduled to run every 30 to 60 seconds.

To reproduce

Install gogs via Docker

Expected behavior

Expect no errors that lead you believe somebody is trying to connect to the service

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
started
started time in 1 day ago
Activity icon
issue

fivenull issue comment gogs/gogs

fivenull
fivenull

error: kex_exchange_identification in logs

Gogs version

0.13.0+dev

Git version

  • Server: 2.32.0
  • Client: n/a

Operating system

Docker version 20.10.5+dfsg1, build 55c4c88 on Debian 11.2 (armv7l)

Database

postgresql-13.4-2

Describe the bug

Once a minute I see the following posted to logs:

Jan 16 03:25:43 sshd[124]: error: kex_exchange_identification: Connection closed by remote host
Jan 16 03:25:43 sshd[124]: Connection closed by 127.0.0.1 port 34959

ssh access works. Just curious what the errors are.

The two errors appear as if scheduled to run every 30 to 60 seconds.

To reproduce

Install gogs via Docker

Expected behavior

Expect no errors that lead you believe somebody is trying to connect to the service

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
fivenull
fivenull

我不是很理解,我也发生了如上错误,该如何处理

started
started time in 1 day ago
Activity icon
issue

stypr issue comment gogs/gogs

stypr
stypr

SSRF in repository migrate via CRLF injection

This is a placeholder issue for CRLF injection in Git which leads to SSRF using repository migrate feature.

Credit to @stypr

stypr
stypr

Marked CVE-2021-32408

push

unknwon push gogs/gogs

unknwon
unknwon

docs: update release templates and playbook (#6735)

[skip ci]

commit sha: 2071eb634f33bb160ba86f79b2de06f122971279

push time in 1 day ago
Activity icon
delete

unknwon in gogs/gogs delete branch unknwon-patch-1

deleted time in 1 day ago
pull request

unknwon pull request gogs/gogs

unknwon
unknwon

docs: update release templates and playbook

Activity icon
issue

unknwon issue gogs/gogs

unknwon
unknwon

Release 0.12.4

Before release

On the release branch:

  • Make sure all commits are cherry-picked from the main branch by checking the patch milestone.
  • Run git log v0.12.1...HEAD --pretty=format:'- [ ] %H %s' --reverse (where v0.12.1 is the last patch release) to get the list of new commits and paste the output below:
    • eb3386c4aac958edc5d592200a892ed3dc3517de context: add X-Frame-Options header (#6411)
    • ec84506da47a187eb6477a78a1fd3d7592082882 repo: disallow urlencoded new lines in git protocol paths (#6420)
    • 5a04c47cf01b5480d3fbfea6df50d5fdd2674299 markup: use default link formation when no format in metas (#6723)
  • Update CHANGELOG on the main branch to include entries for the current patch release.

During release

On the release branch:

  • Update the hard-coded version to the current release, e.g. 0.12.0 -> 0.12.1.
  • Wait for GitHub Actions to complete and no failed jobs.
  • Publish new RC releases (e.g. v0.12.0-rc.1, v0.12.0-rc.2) to ensure Docker wrokflow succeeds. Make sure the tag is created on the release branch.
    • Pull down the Docker image and run through application setup to make sure nothing blows up.
  • Publish a new GitHub release with entries from CHANGELOG for the current patch release and all previous releases with same minor version. Make sure the tag is created on the release branch.
    • Only mention patch authors for the current release.
  • Update all previous GitHub releases with same minor version with the warning:
    *ℹ️ Heads up! There is a new patch release [0.12.1](https://github.com/gogs/gogs/releases/tag/v0.12.1) available, we recommend directly installing or upgrading to that version.**
    ``
    
  • Wait for a new image tag for the current release to be created automatically on both Docker Hub and GitHub Container registry.
  • Update Docker image tag for the minor release <MAJOR>.<MINOR>, e.g. 0.12 on both Docker Hub and GitHub Container registry.
  • Compile and pack binaries (all prefixed with gogs_<MAJOR>.<MINOR>.<PATCH>_, e.g. gogs_0.12.0_):
    • macOS: darwin_amd64.zip, darwin_arm64.zip
    • Linux: linux_386.tar.gz, linux_386.zip, linux_amd64.tar.gz, linux_amd64.zip
    • ARM: linux_armv7.tar.gz, linux_armv7.zip, linux_armv8.tar.gz, linux_armv8.zip
    • Windows: windows_amd64.zip, windows_amd64_mws.zip
  • Generate SHA256 checksum for all binaries to the file checksum_sha256.txt.
  • Upload all binaries to:
  • Update content of Install from binary.

After release

On the main branch:

  • Post the following message on issues that are included in the patch milestone:
    The <MAJOR>.<MINOR>.<PATCH> has been released that includes the patch of the reported issue.
    
  • Update the repository mirror on Gitee.
  • Reply to the release topic for the minor release in Discussions.
  • Close the patch milestone.
  • Send a tweet.
Activity icon
issue

unknwon issue comment gogs/gogs

unknwon
unknwon

Smart links to other issues and PRs are not generated anymore (>= 0.12)

Describe the bug

Generation of (smart) links to issues and PRs don't work in versions higher than 0.12.

Gogs version and commit

Tried with 0.12.3 (several instances, different servers) and 0.13.0-dev

It happens also in https://try.gogs.io (see attached screenshots)

Git version

$ git version
git version 2.30.1

Operating system

FreeBSD, Debian

Database

PostgreSQL 11, MySQL 5.5

To Reproduce Steps to reproduce the behavior:

  1. open an issue, in the description write the number of another issue, like #2
  2. click on preview, in the rendered preview, #2 is a link to issue number 2
  3. click save, in the rendered page with the new issue, #2 is not a link to issue number 2

Can you reproduce the bug at https://try.gogs.io?

Yes

https://try.gogs.io/14mroot/testing-issue/issues/2

Expected behavior

Write #{issue} and a link to the issue to be rendered

Actual behavior

Wrote #{issue} and a link to the issue is not rendered

Screenshots

Attached are three screenshots with the described behaviour in try.gogs.io gogs-report-1 gogs-report-2 gogs-report-3

Additional context

unknwon
unknwon

The 0.12.4 has been released that includes the patch of the reported issue.

push

unknwon push gogs/docs

unknwon
unknwon

Update install_from_binary.md

commit sha: 01fcf2303dac4e36963b6ee8586df7a02f1b8dff

push time in 1 day ago
started
started time in 1 day ago
started
started time in 1 day ago
Jan
17
2 days ago
Activity icon
fork

Kadantte forked gogs/gogs

⚡ Gogs is a painless self-hosted Git service
Kadantte MIT License Updated
fork time in 1 day ago
Previous