github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea 1.3.0 with SSH server enabled crashes with SIGSEGV when pushing to SSH #1256

New Issue
Closed
opened 2025-11-02 03:54:23 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 03:54:23 -06:00
Owner
Copy Link

Originally created by @lapin-b on GitHub (Nov 18, 2017).

  • Gitea version (or commit ref): 1.3.0
  • Git version: 2.15.0
  • Operating system:
    • Client: ArchLinux
    • Server: Debian Stretch
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: there it is

Description

When I want to push with git push to the included SSH server, Gitea crashes with a SIGSEGV. This crash is easily reproductible.

How to reproduce

  1. Download and install a copy of Gitea 1.3.0 to upgrade an older version
  2. Start it with gitea web with embeded SSH server enabled
  3. git push commits to remote. It should crash with a SIGSEGV

Screenshots

Not revelant

Originally created by @lapin-b on GitHub (Nov 18, 2017). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.3.0 - Git version: 2.15.0 - Operating system: - Client: ArchLinux - Server: Debian Stretch - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: [there it is](https://gist.github.com/lapin-b/d224ce3d375841f0df3f2a5ec48f76d7) ## Description When I want to push with `git push` to the included SSH server, Gitea crashes with a SIGSEGV. This crash is easily reproductible. ### How to reproduce 1. Download and install a copy of Gitea 1.3.0 to upgrade an older version 2. Start it with `gitea web` with embeded SSH server enabled 3. `git push` commits to remote. It should crash with a SIGSEGV ## Screenshots *Not revelant*
GiteaMirror added the issue/duplicate label 2025-11-02 03:54:23 -06:00
GiteaMirror commented 2025-11-02 03:54:24 -06:00
Author
Owner
Copy Link

@pztrn commented on GitHub (Nov 18, 2017):

Looks like https://github.com/go-gitea/gitea/issues/2885

@pztrn commented on GitHub (Nov 18, 2017): Looks like https://github.com/go-gitea/gitea/issues/2885
GiteaMirror commented 2025-11-02 03:54:24 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 18, 2017):

#2923 need to be back port to v1.3 @lafriks

@lunny commented on GitHub (Nov 18, 2017): #2923 need to be back port to v1.3 @lafriks
GiteaMirror commented 2025-11-02 03:54:24 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 18, 2017):

@lunny yes, I will do it

@lafriks commented on GitHub (Nov 18, 2017): @lunny yes, I will do it
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1256
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?